Owner checklist · checked 22 September 2026

From a test APK
to Google Play.

No new domain purchase is needed to proceed. This working HTTPS site, privacy page and support contact can be used now. A branded domain can be added later. The app does not need a paid AI API, SMS provider or online backend.

1. Finish account verification

Open Play Console as the owner. Complete identity/contact tasks and any Android device or package-registration task shown. Device verification for new personal accounts uses the Play Console mobile app on a real, non-rooted Android 10+ device. The current account dashboard—not a screenshot from yesterday—is authoritative.

2. Create or open the existing app

Do not create a duplicate. Suggested name: Little Steps: Tiny Routines; default language: English; suggested category: Parenting. Decide Free/Paid deliberately: a free-download package cannot later become a paid-download package. No real-money billing is implemented.

3. Review audience and health classification

Children are genuinely in the audience, so Families requirements apply. Select only ages the actual product serves and has been tested with.

Correction to the earlier checklist: do not automatically select “no health features” just because the app is offline or says it is not treatment. Google’s form includes relaxation and mental/behavioral support. Compare the actual features and claims with the definitions. Resolve uncertainty with Play support. Health-app classification can require an organization account; the Parenting label does not override that.

4. Complete listing and App content

Use the current phone/tablet screenshots, icon, feature graphic, description, privacy URL and support email. Complete ads, App access, IARC rating, target audience/Families, Data Safety, Health apps and any other declarations shown. No account is needed for review: reviewers set any six-digit parent PIN during setup and use it for Parent space.

5. Upload the signed bundle

Use app-release-play-upload.aab, not the test APK and not the unsigned raw bundle. On the development PC it is under:

little-steps/app/build/outputs/bundle/release/app-release-play-upload.aab

Version 0.15.0-pip-home; code 20; package eu.littlesteps.app; target API 36. Keep the existing upload key. Stop and inspect certificate/version errors instead of regenerating keys.

6. Set up the closed track

Add all 15 invited Google accounts and the tester countries, upload the signed AAB and submit the release. Google’s review controls when it becomes available. Once active, copy the opt-in link from the track’s Testers tab. Friends must opt in with the invited account and install from Play—not only the website APK.

For new personal accounts created after 13 November 2023, at least 12 must remain opted in continuously for 14 days before applying for production access. Genuine testing and feedback are required; do not fabricate them.

7. Check real devices and apply when eligible

Use the device checklist and Play pre-launch report. Test notification permission changes, PIN relock, media, offline voice, accessibility and Android 16 behavior. Then apply for production access and report the real feedback. The 14-day threshold does not guarantee approval.

Also verify publisher/trader contact details, applicable legal/privacy notices and commercial rights for all media before public production. Automated unit tests are not a legal or clinical certification.

Data and signing: the downloadable debug APK and Google Play build may not update over each other because of different certificates. Do not uninstall or clear a family’s only app data to force an update. There is no cloud restore; use a separate test device/profile or resolve a transfer plan.

Official references

Closed-test requirements · Device verification · Privacy policy requirements · Health apps form · Account requirements · Families · Free and paid apps

No Google Play upload or rollout has been performed by this update.