An Android Internal Testing Readiness Checklist
Internal testing is not a public launch. It is the proof loop that makes the Android app, the product page, and the privacy story line up before wider release.
Use the current public state
A product page should use Available only when the public store page works. In review, Testing, and Coming soon are different states and should remain visibly distinct. Collectory is now available on Android while its iPhone release is in review.
Make the trust path testable
Before inviting testers, the privacy policy, support path, backup language, local storage notes, and known limits should already match the app. Testers should understand that no account is required, collection data is local-first, photos stay on device unless exported, and backup or restore flows are user-controlled.
Turn tester notes into launch fixes
Internal testing should capture confusing copy, broken restore paths, unclear location labels, missing empty states, and places where the public promise feels too broad. The goal is not to hype the app early; it is to make the first public version simpler, safer, and easier to explain.