App does not have a template-generated appearance
Why it matters
Apple's guideline 4.3 (spam) targets apps that are "simply a generic interface without any realistic functionality" — which includes template-generated apps with the default Expo blue-circle icon, placeholder names like "MyApp" or "React Native App," and screens with no purposeful content beyond boilerplate. Apps that look like templates attract heightened review scrutiny on all other guidelines. The ISO 25010:2011 functional-completeness classification applies: an app that hasn't been customized beyond a starter template provides no functional value beyond what the template itself provides.
Severity rationale
Info because this is a risk-indicator rather than a hard failure — template appearance attracts scrutiny but is not a standalone rejection cause by itself.
Remediation
Replace default template assets and placeholder strings before generating the submission build.
In app.json, verify:
{
"name": "YourActualAppName",
"slug": "your-actual-app",
"icon": "./assets/images/icon.png"
}
The ./assets/images/icon.png file must not be the default Expo solid-blue-circle. Use a 1024×1024 custom icon with your actual branding. In your strings files (ios/MyApp/Info.plist, android/app/src/main/res/values/strings.xml), replace app_name = "MyApp" with your real app name. Search your source for HomeScreen, Screen1, MainScreen and verify each has app-specific content, not boilerplate placeholder text.
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 Review Blockers Audit. The pattern definition, severity rationale, and remediation remain openly licensed under CC-BY-4.0.
External references
- external · apple-guideline-4.3-spam — Apple App Store Review Guideline 4.3 — No Spam or Template-Generated Apps
Taxons
History
- 2026-04-18·v1.0.0·Initial import from app-store-review-blockers·automated