App name is consistent across platforms
Why it matters
Divergent app names between iOS and Android fracture brand recognition at the exact moment a user is deciding to install. Reviewers cross-checking listings flag the mismatch as a submission-quality concern, support tickets pile up when users search a store for a name that does not exist there, and paid acquisition attribution breaks because the install surface labels do not match the campaign creative. This operational-readiness defect also leaks into OS-level UI — home-screen icons, notification banners, and share sheets — turning every touchpoint into a trust deduction.
Severity rationale
Medium because the inconsistency damages brand trust and discoverability but does not block store approval or break app functionality.
Remediation
Pick a single canonical display name and propagate it across every platform surface. Update app.json name, android/app/src/main/res/values/strings.xml app_name, and the Xcode target Display Name to the identical string, then rebuild both binaries and verify the home-screen label on a physical device for each OS.
// app.json
{ "name": "MyApp Pro" }
<!-- android/app/src/main/res/values/strings.xml -->
<string name="app_name">MyApp Pro</string>
DetectionPro
The detection method for this pattern is part of AuditBuffet Pro.
The full method (what to look for, pass and fail conditions, and how results get reported) ships inside the App Store Readiness Audit. The pattern definition, severity rationale, and remediation remain openly licensed under CC-BY-4.0.
Taxons
History
- 2026-04-18·v1.0.0·Initial import from mobile-store-readiness·automated