canmove, Confirmed users
1,577
edits
Platform/Features/Notifications: Difference between revisions
→Release Requirements
(→Team) |
|||
| Line 55: | Line 55: | ||
== Release Requirements == | == Release Requirements == | ||
1. We need to feel that the public web API is solid enough to put into a release. Prefixed is OK, or private, depending on if we want to put this on a standards tracks or re-use existing APIs (like Event Source.) | |||
2. We'll need to have a server set up so that developers can use this feature easily without having to launch their own services. | |||
3. Although this is not required for initial launch, we need to have a clear path on Mobile and make sure that any APIs we deploy will work on Mobile as well as desktop. Also required is a path that lets us deploy at scale on Mobile in a way that won't drain batteries excessively. | |||
4. We'll have to go through security reviews for the design and implementation. | |||
5. We should try and stagger the release into useful bits to start getting useful feedback. Stages are laid out above. | |||
6. The implementation should be deploy-able and support-able. | |||
== Next Steps & Open Issues == | == Next Steps & Open Issues == | ||