This is an attempt to sketch out some high-level milestones for discussion.
Currently we have a trusted tester program ongoing, where we've been targeting getting devs able to use Shorebird to push to small usage apps (e.g. 10k users). https://github.com/shorebirdtech/shorebird/blob/main/TRUSTED_TESTERS.md
Right now we're trying to "find the product". See if we can build something that people want and will use and pay for. We're not trying to "build it right" yet, but we are trying to build things that are in the directions we think they will need to grow in.
For example. Right now we have a manual sign-up process. We send folks an email with a Stripe link, they fill it out, Zapier then notifies us in our Discord channel, we manually create an API key, manually report that back to the Discord channel, and manually email it to the user. It's terrible. But importantly it lets us build in the direction we're going (of building a paid product) even if we don't have anything resembling the final flow yet and as terrible as it is, it's good enough to unblock us testing the rest of the system.
We have lots of untested code (not because we don't like tests), but because we're not sure if we'll have that code in a few weeks time.
Anyway, this doc is about figuring out what is the next thing we're questing towards and then we will hack and slash our way there.
Milestones are roughly ordered how I expect us to approach them:
- Async updates / make updates only download on WiFi?
- Ability to upgrade Flutter in < 1hr
- Ability to ship updates to
shorebirdin < 1hr shorebirdassets built reliably in the cloud.- Ability to patch/test an app built with earlier Shorebird?
- Some kind of promotion mechanism (e.g. channels)
- Some kind of analytics (how many updates were served for a given app)
- Dart access to updater API for control of updates?
- Anti-DDoS (some sort of update rate limiting)
- CDN for Updates?
- CLI support for Windows
- Publicly available sign-up flow (including billing)
- Ability