Make a start on Trusted Tester documentation

Lots more to write.

TODO.md

@@ -4,21 +4,6 @@
 - We believe Flutter is that default, but has missing pieces for enterprises.
 - The first hole we're filling is the ability to push updates to Flutter apps.
 
-## This Week's Demo
-
-- Platform support (e.g. push to both arm7 and arm64)
-- API Keys and/or app ids (allows multiple users)
-- Teach the server how to decline to update (e.g. platform/version mismatch).
-- Instructions on how to build/use.
-
-## User journey
-
-Someone can:
-
-- download and install Shorebird.
-- `shorebird build` their existing Flutter app.
-- Push an update to their app.
-
 ## Shipping to users (first, do no harm)
 
 - Need a way to know if the update failed (and both report it and roll back?)

TRUSTED_TESTERS.md

@@ -0,0 +1,106 @@
+# Trusted Testers
+
+While this document is public, access to Shorebird services are not yet
+generally available. We're running a trusted tester program with a limited
+number of users to ensure that we're building the right thing and that it's
+stable for general use.
+
+If you'd like to be a part of the program, please join our mailing list
+(linked from shorebird.dev), we will send out information there as we're ready.
+
+
+
+## Welcome!
+
+If you're joining the trusted tester program, welcome!  Thank you for your help
+making Shorebird a reality.
+
+You should have received an API key in the mail.  You will need it as part
+of the login process for the `shorebird` command-line tool to work.
+
+## Our goal
+
+Our goal with this Trusted Tester program is to shake out bugs and ensure that
+we are building things people want.  We *want* your feedback.  We *want* you to
+break things.  We *want* you to tell us what you want to see next.  We're
+already a default-public company, but we intend to be even more open with you
+and will be shipping your regular updates during the program, responding to
+your feedback.
+
+Our guiding principle in creating v1 is "first, do no harm".  It should be the
+case that using Shorebird is never worse than not using Shorebird.  We've worked
+hard to find and remove breaking bugs.
+
+It is still possible using Shorebird
+may break your app in the wild.  Thankfully this is no worse than any other
+change to your app, and you can always push a new version via the store should
+Shorebird break users in the wild.
+
+## What works today
+You can build and deploy new (release) versions of your app to all Android arm64
+users via Shorebird command line from a Mac computer.
+
+All users will synchronously update to the new version on next launch
+(no control over this behavior yet).
+
+Basic access to the updater through package:dart_bindings (unpublished).
+
+Shorebird command line can show a list of what apps and app versions you've
+associated with your account and what patches you've pushed to those apps.
+
+Updates are currently typically a few MBs in size and include all Dart code that
+your app uses (we can make this much smaller, but haven't yet).
+
+## What doesn't yet
+
+Limited platform support:
+* Only Arm64 platform, no non-Android or non-arm64 support.
+* Windows, Linux
+
+No support for:
+* Flutter channels (only latest stable is supported)
+* Rollbacks
+* Channels
+* Percentage based rollouts
+* Async updates
+* Analytics
+* Web interface
+* CI/CD (GitHub Actions, etc.)
+* Patch signing
+* OAuth (or associating with any other accounts)
+
+## Getting started
+
+The first thing you'll want to do is install the `shorebird` command-line tool.
+
+// Insert instructions here.
+
+Currently we assume you have `flutter` installed and working.  We also require
+that `flutter` be set to the latest stable channel.  The `shorebird` tool should
+enforce this (and show errors if your `flutter` is not set up as expected).
+
+
+## What next?
+
+The first use-case we're targeting is one of deploying updates to a small
+set of users.  If you already have a Flutter app with a small install base, you
+can convert it to Shorebird in a few steps:
+
+1. Use `shorebird init` to add a `shorebird.yaml` file to your project.
+`shorebird.yaml` contains the app_id for your app, which is just a unique
+identifier the app will be able to send to Shorebird servers to identify which
+application/developer to pull updates from.
+
+`shorebird init` will also add the `shorebird.yaml` to the assets section of
+your `pubspec.yaml` file, which will ensure that the file is included in your
+app's assets.
+
+You can go ahead an commit these changes, they will be innocuous even if you
+don't end up using Shorebird with this application.
+
+2.  Typical development usage will involve normal `flutter` commands.  Only
+when you go to build the final release version of you app, do you need to use
+the `shorebird` command-line tool.
+
+
+// More here.