release: seal Focus Seed 1.0.0
This commit is contained in:
@@ -0,0 +1,128 @@
|
||||
# Region And Localization Strategy
|
||||
|
||||
Status: V1 launch guardrail for Focus Seed.
|
||||
|
||||
## Principle
|
||||
|
||||
Focus Seed is intended to become a global productivity app, but V1 should not open every country by default. The first release is for account rescue, policy safety, and product validation. Availability, language, privacy wording, and monetization should expand by region only when the app has the right local readiness.
|
||||
|
||||
Google Play country targeting is based on the user's Play country, not the user's current physical location. Internal testing is the exception: internal testers can receive the app even if their country is not selected for production/open/closed tracks.
|
||||
|
||||
## V1 Recommended Launch Scope
|
||||
|
||||
Use English-only store listing and app UI.
|
||||
|
||||
Recommended first production or closed-test countries/regions:
|
||||
|
||||
- United States
|
||||
- Canada
|
||||
- Australia
|
||||
- New Zealand
|
||||
- Singapore
|
||||
- India
|
||||
- Philippines
|
||||
- Malaysia
|
||||
|
||||
Rationale:
|
||||
|
||||
- English is broadly usable in these markets.
|
||||
- The app is culturally neutral: focus timer, habit tracking, local reflection.
|
||||
- V1 has no account, no server, no ads, no analytics, no billing, and no sensitive permissions.
|
||||
- This avoids adding rushed EU/EEA, Korean, Japanese, or other local-language obligations during the dormant-account rescue window.
|
||||
|
||||
If only internal testing is used for urgent account activity, do not over-optimize regions yet. Upload the AAB, finish required declarations, and keep the country plan ready for the first closed/open/production rollout.
|
||||
|
||||
## Regions To Defer
|
||||
|
||||
Defer EU / EEA until a later release unless there is a clear need:
|
||||
|
||||
- Add EU/EEA privacy wording and legal review.
|
||||
- Confirm trader / non-trader presentation requirements shown in Play Console.
|
||||
- Review geo-blocking and country availability choices.
|
||||
- Confirm consent flow if ads, analytics, remote config, crash reporting, or cloud sync are added later.
|
||||
|
||||
Defer United Kingdom and Switzerland if the goal is the simplest possible legal surface. They are English-friendly but should still get region-specific privacy review before paid or data-collecting features.
|
||||
|
||||
Defer South Korea:
|
||||
|
||||
- No Korean localization in V1.
|
||||
- Review local rating, local store expectations, and translated listing before launch.
|
||||
|
||||
Defer Japan:
|
||||
|
||||
- No Japanese localization in V1.
|
||||
- Productivity apps can work there, but store conversion and support quality need Japanese copy.
|
||||
|
||||
Defer Brazil / LATAM:
|
||||
|
||||
- Add Portuguese or Spanish listing and privacy/support wording first.
|
||||
|
||||
Defer Middle East / North Africa:
|
||||
|
||||
- Keep the app culturally neutral, but review local listing language and screenshots before expansion.
|
||||
|
||||
## Store Listing Language
|
||||
|
||||
V1:
|
||||
|
||||
- Default language: English (United States).
|
||||
- Do not add machine-translated Korean, Japanese, German, French, Spanish, or Portuguese just to look global.
|
||||
- Do not claim local-language support that the app does not provide.
|
||||
|
||||
Wave 2:
|
||||
|
||||
- English variants for UK/Australia only if those regions are opened.
|
||||
- Spanish or Portuguese only after translated screenshots and support text exist.
|
||||
|
||||
Wave 3:
|
||||
|
||||
- Japanese and Korean only after native-quality listing, screenshots, and cultural QA.
|
||||
|
||||
## Privacy And Data Safety
|
||||
|
||||
V1 privacy posture:
|
||||
|
||||
- No account.
|
||||
- No server.
|
||||
- No analytics SDK.
|
||||
- No ad SDK.
|
||||
- No billing SDK.
|
||||
- No network permission.
|
||||
- Local-only user-controlled data.
|
||||
|
||||
Even when no data is collected, Google Play still requires accurate Data safety answers and a privacy policy for published/testing apps outside internal-only use. Do not use region selection as an excuse to make inaccurate privacy statements.
|
||||
|
||||
If any of the following are added, revisit every target region before release:
|
||||
|
||||
- Ads
|
||||
- Analytics
|
||||
- Crash reporting
|
||||
- Remote config
|
||||
- Billing or subscriptions
|
||||
- Cloud backup/sync
|
||||
- Login/account creation
|
||||
- Push notifications
|
||||
- Location, contacts, calendar, storage, health, finance, or other sensitive data
|
||||
|
||||
## Culture And Content Guardrails
|
||||
|
||||
Keep V1 content neutral:
|
||||
|
||||
- No religious, political, medical, financial, gambling, dating, or adult claims.
|
||||
- No children-directed positioning.
|
||||
- No culturally specific imagery or slogans in screenshots.
|
||||
- No productivity claims that imply clinical treatment or guaranteed outcomes.
|
||||
- Use plain, calm English and avoid idioms that translate poorly.
|
||||
|
||||
## Expansion Checklist
|
||||
|
||||
Before adding a new region:
|
||||
|
||||
1. Confirm the app UI language and store listing language fit the region.
|
||||
2. Confirm privacy policy and support email wording fit the region.
|
||||
3. Confirm Data safety answers still match the shipped build.
|
||||
4. Confirm content rating and target audience are appropriate.
|
||||
5. Confirm screenshots do not include culturally sensitive text or imagery.
|
||||
6. Confirm ads/subscriptions, if added, are available and priced correctly for that country.
|
||||
7. Run at least one smoke test for the exact build being released.
|
||||
|
||||
Reference in New Issue
Block a user