Guideline 4.3
Guideline 4.3(a) - Design: Spam - Same App Under Multiple Bundle IDs
Our Take
Apple is rejecting your app because they have identified it as substantially similar to another app already on the App Store — either one you've submitted yourself or one from another developer. Guideline 4.3 targets app spam: submitting the same app multiple times under different names, bundle IDs, or developer accounts to game search rankings or saturate a category. This rejection most commonly hits developers who white-label their app for multiple clients (submitting essentially the same binary with different branding), developers who submit regional variants of the same app as separate listings, or developers who create multiple apps with minor feature differences to occupy more search result slots. Apple's automated systems now detect binary similarity, shared code signatures, and matching asset patterns across submissions. Even if you change the app name, icon, and color scheme, if the underlying binary is substantially the same, Apple will flag it. The fastest compliant path is to consolidate your apps into a single listing with in-app configuration (e.g., region selection, brand theming, or account-based customization). If you genuinely have different apps for different audiences, you need to demonstrate clear, substantial differentiation — different features, different content, different user flows — not just different skins.
Resolution Guide
Create a single universal app
Build one app that supports multiple brands, regions, or configurations through in-app settings.
Implement in-app brand switching
Let users select their brand/organization during onboarding. Store the configuration and adjust UI theming, content, and backend endpoints accordingly.
Remove duplicate listings
After your consolidated app is approved, remove the duplicate app listings from App Store Connect.
Redirect existing users
Use the remaining listings to display an update message directing users to the consolidated app before removing them.
### Path B: Demonstrate differentiation
Document unique features per app
Create a feature comparison matrix showing what each app does differently. Apple wants to see distinct functionality, not just different content.
Differentiate the user experience
Different workflows, different interaction models, different navigation structures. Skin-deep changes (colors, logos, copy) don't count.
Target different audiences
Each app should serve a genuinely different user need. 'Restaurant A' and 'Restaurant B' are the same need; 'Restaurant ordering' and 'Kitchen management' are different needs.
Respond with evidence
In the Resolution Center, provide detailed screenshots and feature lists for each app showing the substantial differences.
Prevention
Example Rejection Email
Consider Appealing
Appeal only if the apps are genuinely different products with distinct functionality, content, and user bases. Provide a detailed feature comparison matrix showing the differences. If the apps are truly the same app with different branding, do not appeal — consolidate and resubmit.
Before & After
Developer has 8 city guide apps (NYC Guide, LA Guide, Chicago Guide, etc.) each with the same binary, UI, and features — just different city data loaded from a config file
Single 'City Guide' app with city selection on first launch, all cities available in-app with the ability to switch or add favorites, unified notification preferences per city
What changed: Multiple apps with the same binary and different data configurations must be consolidated into a single app with in-app selection.
Community Solutions · 0
Sign in to share your solution.
More Guideline 4 (Design) rejections
- Guideline 4.0 - Design: App Does Not Include iOS Features
- Guideline 4.0 - Design: App Looks Like a Website
- Guideline 4.0 - Design: Apple Pay Button Not Following Guidelines
- Guideline 4.0 - Design: Blurry Icons or Low-Resolution Assets
- Guideline 4.0 - Design: Broken Layout on iPad
- Guideline 4.0 - Design: Content Clipped by Notch or Safe Area