Congratulations to everyone for hitting the beta milestone and delivering a major Q2 objective! Beta on mainnet has been no small feat.
As the dust settles from the beta launch we can all turn our focus to the next major milestone, launching publicly on the iOS App Store and Android Play Store! But that raises the question, what are our must-haves and hard blockers? And do we have any time constraints?
Just as we had a security audit as a hard blocker for beta, Status will again undergo a security audit for the public launch. The audit is expected to run from September 15-30 with a feature freeze before that. After the audit concludes there will be time to implement fixes, as well as undergo a few weeks of final testing before launch.
The audit and feature freeze gives us a deadline to prioritize what will provide Status the best foundation for launch. Any major new features will need to be included before the feature freeze if we want to launch with a fully audited app.
As for must-have features, that decision is in the hands of the community and teams. Please comment here with what Status needs for the public launch to be both a quality launch and also embody our values. Or alternatively we may have everything we need ready to go?
So far I’ve heard some of these suggestions:
- Seamless upgrades
- Solid chat encryption (eg forward secrecy, double ratchet)
- ENS support
- LES protocol as an option, as well as user defined RPC
- Better chat moderation and spam prevention
- Replacing Mixpanel
- More SNT utility
- Responding to bugs/features/issues/requests surfaced in the beta by users
- Multiple languages
- We don’t need anything else. Let’s harden the beta and get it audited and ship!
Do these need to be in the public launch? Anything else? Or are we already set with the beta scope? Please let us know!
(And ideally please make an argument about why it is essential to the public launch. Do we absolutely need to have it? Should the launch be blocked for feature X? Or can it wait a future version? The public launch is just the beginning and we have years ahead of us to keep building on our foundation so we have to be diligent and mindful about what is essential and what can wait.)
One major concern is that new work or features that weren’t in the audit scope may mean that we will either ship features that haven’t been audited, or will require a third audit, or some other solution. We should gauge our comfort level around these constraints.
Once the issues are discussed and finalized we can continue with a launch milestone on Github with blockers and must-haves to give org-level visibility.
edit: changed “1.0” to “public launch”