Clarified experimental nature of crux in its own section, which state…

docs/src/overview.md

@@ -1,6 +1,6 @@
 # Overview
 
-Crux is an **experimental** approach to building cross-platform applications
+Crux is an approach to building cross-platform applications
 with better testability, higher code and behavior reuse, better safety,
 security, and more joy from better tools.
 
@@ -66,7 +66,7 @@ will result in build failures in the Shell.
 
 ## Goals
 
-We set out to prove this architecture to find a better way of building apps
+We set out to find a better way of building apps
 across platforms. You can read more [about our motivation](./motivation.md). The
 overall goals of Crux are to:
 
@@ -78,3 +78,20 @@ overall goals of Crux are to:
 - Separate the behavior from the look and feel and interaction design
 - Use the native UI tool kits to create user experience that is the best fit for
   a given platform
+
+## Path to 1.0
+
+Crux is used in production apps today, at least one quite large one. In that sense
+we consider it production ready. However, to truly be at 1.0 with a more stable
+API, we will take the following steps:
+
+* Improved documentation, code examples, and example apps for newcomers
+* Improved onboarding experience, with less boilerplate code that end users have
+  to deal with
+* Better FFI code generation to enable support for more Shells (e.g. .NET,
+  Flutter) which will also enable Desktop apps in Windows
+* Revised capabilities and effects to allow
+  for [app composition](./guide/composing.md) in larger apps
+
+Until then, we hope you will work with us on the rough edges, and factor in
+frequent API updates as we evolve.