Mobile-Specific Strategy

Different from web

• Device fragmentation (1000+ Android).
• App store gatekeeper (review delay).
• Offline-first.
• Push notification.
• IAP / subscription.
• Battery / memory budget.
• Background restriction.

Key strategic decisions

Native vs cross-platform

• Native (Swift/Kotlin) — performance, platform feature, separate teams.
• React Native / Flutter — cross-platform, code reuse.
• Test strategy reflects choice.

Device coverage

• Real device farm OR cloud (BrowserStack)?
• 5-10 critical device cover 80% user.
• Tier-1 (test always): Samsung A, Xiaomi mid, iPhone latest 2 gen.

Manual vs automated split

• UI: highly automatable but flaky.
• IAP: must manual (sandbox accounts).
• Localization: visual review essential.

Beta program

• TestFlight (iOS) up to 10K.
• Internal track + Open testing (Android).
• Recruit beta users from real customer.

Release cadence

• Web: deploy continuously.
• Mobile: 1-2 weeks for review + adoption.
• Strategy: feature flag mobile launches.

Mobile-specific KPIs

• App Store rating.
• Crash-free user rate (target > 99.5%).
• ANR rate (Android) < 0.5%.
• App size budget (compressed < 50MB).
• Cold start < 2s.

VN mobile context

• Android dominate 75%.
• Vsmart, Bphone discontinued — Samsung, Xiaomi, Oppo dominant.
• iPhone HCMC/HN tier-1 affluent.
• Old Android (8, 9) still active 30%+ user.

Strategy doc include

• Device matrix.
• OS version support policy.
• Update enforcement (force vs soft).
• Beta program rules.
• Crash budget.