Release readiness
A release checklist for Thai–English mobile launches
Bilingual launches in Thailand often fail soft checks rather than spectacular crashes. The binary works; the listing, screenshots, and privacy answers disagree. This checklist is what we walk during release readiness audits.
Listing claims vs. binary behavior
Read every bullet on the store page, then attempt that behavior in both languages. Features removed mid-sprint still linger in English screenshots while Thai copy was updated — or the reverse. Call those mismatches explicitly in the findings pack.
Locale screenshots
Capture Thai and English UI on the same device class. Truncated Thai labels, overlapping badges, and currency formatting errors show up here more than in design files.
Privacy and data answers
Questionnaire responses should name the same data categories the app actually collects. Payment apps and health booking tools get particular attention: health or financial data claims need to match onboarding disclosures.
Support and account deletion paths
Confirm that support contact details resolve, and that account deletion or data request flows exist when promised. Reviewers and regulators both notice hollow links.
- Primary flows complete in Thai and English
- Screenshots match current UI
- Permission pre-prompts translated and accurate
- Crash-free path through signup and a core transaction
- Privacy answers reviewed by someone who knows the build
Need a coordinated pass? Start with the Full release readiness audit.