We’ve had a half-baked concept for a program called
Optimised for Status going for a while now and would love some input to help us build it out.
Optimised for Status?
Concept: DApps take certain steps to qualify as “optimised for Status” and are rewarded in some way. This could take the form of a badge for their site, an invitation to join a special community, participation as evaluators in a TCR for DApps, etc.
Objective: Incentivise developers to think about the experience of their DApps inside Status and raise the profile of Status developer tools.
- Mobile-optimized—this can be guaged objectively using something like Google Mobile-Friendly Test
- Works on mainnet
- Detects Status host
- Offers directions for using Status in documentation or FAQs
- Links to Status from their site
- Use Status APIs or SDKs…?
The criteria are definitely open to further input, and will require a greater level of specificity.
What I’d most like to hear suggestions about is incentives for participation.
Many of these criteria are low-hanging fruit. Mobile optimisation, mainnet and great user guides are prerequisites for any successful DApp (Status-specific user guides not so much, but many are written with MetaMask in mind and we’d like Status featured, too).
For those that go the extra mile to integrate with Status, we’d like to offer you recognition, access, community and support.
Apart from featuring your DApp in our curated list and offering—hopefully—great developer tools, what else can we do for you?