How we score
There is no industry standard for "percent done." This score is our own rubric. We publish it so you can judge it.
Each product gets up to 100 points. A point counts only when there is proof: a test run, a build, a screenshot or a video.
| Area | Points | Proof we need |
|---|---|---|
| Core features work end to end | 25 | Each feature shown (test or video timestamp) |
| Tests exist and pass | 15 | Command, exit code, pass/fail/skip |
| Reproducible build/artifact | 15 | CI on main + local build exit 0 + artifact path |
| Security & privacy | 10 | Secret scan, dep audit, permissions justified, privacy policy |
| Docs | 10 | Accurate README, install works, user guide |
| Accessibility & UX | 10 | Contrast, dark mode, keyboard/TalkBack basics, reduced-motion option |
| Distribution readiness | 10 | Android: icon, listing, screenshots, data safety, signed release. Desktop/web: installer or URL |
| Ops hygiene | 5 | Version, changelog, error handling, LICENSE |
What the stages mean
- 0 to 24: Pre-alpha
- 25 to 59: Alpha
- 60 to 84: Beta
- 85 to 99: Release candidate
- 100 with a stable interface: 1.0
Android apps also show where they are on Google Play: not on Play, internal test, closed test, open test or production.
Common questions
- Is this score an industry standard?
- No. There is no industry standard for "percent done." This score is our own rubric, and we publish the whole rubric so you can judge it.
- What makes a point count?
- Proof. A point counts only when there is a test run, a build, a screenshot or a video behind it.
- Why is none of your Android apps on Google Play?
- Google Play asks new developer accounts to run a closed test with at least 12 testers for 14 days in a row before an app can go to production. Our Android apps have not done that test yet.
- How can I check what you say about a product?
- Each product page lists what works today and what is not finished, and each comparison table says under it where its facts came from.