tatmapper-app

Google Play release runbook

Status: preparation only. No TatMapper artifact has been uploaded by this pass.

Public support and technical contact: tatmapper@gmail.com. The Play Console owner/login may use a separate secured Google account.

Verified repository boundary

• Package: com.tatmapper.app
• Version name: 2.0.0
• Next repository version code: 4
• Minimum SDK: 24
• Target/compile SDK: 36
• Monetized test build: camera, Internet, Play Billing, and advertising ID; Google Mobile Ads/UMP; no TatMapper analytics, account, or telemetry
• Android cloud backup and device transfer: all app data excluded

Repository and GitHub history do not show a Play upload of version code 3. Play Console remains authoritative. Before the first upload, the owner must confirm the highest existing version code. If 4 is already used, choose one higher unused value once and record it in the release evidence.

Google’s current policy requires new apps and updates to target an API level within one year of the latest major Android version; from 31 August 2026, ordinary new apps and updates must target API 36 or later. TatMapper targets 36. Official policy

Safe release sequence

1. Merge PR #101 only after review and explicit authorization.
2. Retarget PR #108 to main, inspect the entire diff, rerun all gates, and merge only with separate authorization.
3. Repeat for PR #110.
4. Retarget PR #118, inspect and rerun all gates, and merge only with separate authorization.
5. Create a clean release-candidate branch from updated main.
6. Confirm Play’s highest version code, final support/privacy URLs, declarations, exact binary behavior, AdMob approval, active tatmapper_pro base plans, UMP messages, and production entitlement verifier.
7. With the owner present, configure the upload key and Play App Signing.
8. Build the release AAB, record source SHA, version, byte size, SHA-256, upload certificate fingerprint, mapping file, and native symbols.
9. Upload only to Internal testing after explicit authorization.
10. Review the automated pre-launch report’s Stability, Compatibility, Performance, Accessibility, and Screenshots evidence.
11. Run the structured shop checklist, then create a Closed test.
12. If the developer account is a newly created personal account after 13 November 2023, keep at least 12 testers continuously opted in for at least 14 days before applying for production access. Official testing requirement
13. Answer production-access questions from actual tester engagement and defects. Do not invent feedback.
14. Use a staged production rollout only after approval and separate owner authorization.

Google documents that pre-launch reports exercise stability, compatibility, performance, and accessibility, but they do not replace physical printer testing. Pre-launch report guide

Multi-project library decision

Issue #119 is not required to create the Play record or begin Internal/Closed testing. It is strongly recommended before broad public Production because a working artist commonly needs multiple active client projects. The production decision should be revisited after structured shop testers report whether the single-project limitation disrupts real work.