Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore: Add more notes to todo. #16

Merged
merged 3 commits into from
Mar 6, 2023
Merged

chore: Add more notes to todo. #16

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
cfb7c25
Create TODO.md
eseidel Mar 5, 2023
8160558
Merge branch 'shorebirdtech:main' into main
eseidel Mar 6, 2023
020b2c0
Update TODO.md
eseidel Mar 6, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
24 changes: 19 additions & 5 deletions TODO.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,15 +1,29 @@
This Week's Demo
## A reminder why
* We're here to make multi-platform the default.
* 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 (allows multiple users)
* Separate product ids (allows multiple users)
* API Keys and/or product 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:
## User journey
Someone can:
* download and install Shorebird.
* `shorebird build` their existing Flutter app.
* Push an update to their app.

Later
## Shipping to users (first, do no harm)
* Need a way to know if the update failed (and both report it and roll back?)
* Need to not send updates to incompatible devices or base versions.
* Do we need to worry about different chipsets?
* How do we educate users/developers about data storage updates (e.g. updating a database schema locally) and how that affects version compatibility / ability to roll back?
* How does the Dart code know that it's running a patched version?

## Later
* Way to see what builds have been published so far.
* See what % of devices are running what builds.
* Make package:updater API work from Dart
Expand Down