# Guideline 4.3(a) - Design - Spam: Similar Binary or Metadata **Guideline:** 4.3(a) · **Store:** Apple App Store · **Risk:** high · **Difficulty:** hard · **Typical turnaround:** 1-4 weeks Canonical URL: https://appstorereject.com/rejections/apple/4/guideline-43a-design-spam-similar-binary-or-metadata ## Description Apple determined that your app shares a similar binary, metadata, and/or concept as apps submitted to the App Store by other developers, with only minor differences. This is a specific variant of the 4.3 Spam guideline targeting apps that appear to be repackaged or cloned versions of existing apps — even if developed by different accounts. Unlike a general 4.3 duplicate rejection (which may target your own duplicate submissions), 4.3(a) flags similarity to other developers' apps. However, Apple frequently classifies the wrong app as a spam or duplicate app. If you believe yours was the original to use your code and metadata, appeal the rejection with the required concrete evidence of uniqueness. ## Common variations - App shares a similar binary, metadata, and/or concept as apps submitted by other developers - App appears to be built from a commercially available template or app builder - App binary is substantially similar to another app already on the App Store - Multiple submissions across different developer accounts with similar functionality - App purchased from a template marketplace flagged as a known spam source - App wrapper around a website with no native functionality ## Example rejection email ``` We noticed the app shares a similar binary, metadata, and/or concept as apps submitted to the App Store by other developers, with only minor differences. Submitting similar or repackaged apps is a form of spam that creates clutter and makes it difficult for users to discover new apps. Next Steps Since we do not accept spam apps on the App Store, we encourage you to review the app concept and submit a unique app with distinct content and functionality. Resources Some factors that contribute to a spam rejection may include: - Submitting an app with the same source code or assets as other apps already submitted to the App Store - Creating and submitting multiple similar apps using a repackaged app template - Purchasing an app template with problematic code from a third party - Submitting several similar apps across multiple accounts ``` ## Resolution steps 1. **Identify the source of similarity** — Determine why Apple flagged your app. If you used a template, app builder (e.g., BuildFire, Appy Pie, GoodBarber), or purchased source code, this is likely the trigger. Search the App Store for apps that look similar to yours. 2. **Rebuild with substantial custom code** — If your app is template-based, you need to rewrite significant portions. A reskin with new colors and assets is not enough — Apple compares binaries, not just UI. Aim for at least 60-70% original code. 3. **Differentiate your concept and metadata** — Change your app name, subtitle, keywords, and description so they don't overlap with similar apps. Apple checks metadata similarity alongside the binary. 4. **Add unique, meaningful features** — Implement functionality that no similar app offers. This could be unique data sources, novel UI interactions, platform integrations, or specialized workflows for your target audience. Cosmetic differences alone won't suffice. 5. **Remove template boilerplate** — Strip out unused template screens, placeholder content, default assets, and any code paths that aren't relevant to your app's core purpose. Template remnants are a strong signal to reviewers. 6. **Use original assets** — Replace all stock images, icons, and default UI components with custom-designed assets. Matching visual identity to other template apps is a red flag. 7. **Write a detailed appeal** — In your App Review response or resubmission notes, explain your app's unique value proposition, your target audience, and how it differs from similar apps. Reference specific features that are original. 8. **Consider a fresh submission** — If the rejection persists, it may help to create a new app record in App Store Connect rather than resubmitting the same one, especially if the review history is heavily flagged. ## Appeal guidance A 4.3(a) appeal requires concrete evidence of uniqueness. In your response: (1) Acknowledge the concern respectfully, (2) List specific features unique to your app with screenshots, (3) Explain your custom codebase — mention the language, frameworks, and original architecture, (4) If you used a template as a starting point, explain how much was rewritten and what's original, (5) Provide a comparison table showing differences from the similar apps Apple may have flagged. If you genuinely built everything from scratch and believe this is a false positive, say so clearly and offer to schedule a call or provide source code access. ## Before / after examples **Before:** App built using a popular no-code platform with default templates, resulting in a binary nearly identical to hundreds of other apps on the Store **After:** Rebuilt core features natively in Swift, kept the no-code backend for content management but all client-side code is original with custom UI components **Why it works:** Template-based apps share binary signatures that Apple detects automatically. Native code eliminates this similarity. **Before:** Purchased source code from CodeCanyon, changed the branding and content, submitted under a new developer account **After:** Used the purchased code as a learning reference only, rewrote the app from scratch with a unique architecture, original API integrations, and a distinct feature set **Why it works:** Reskinning purchased code doesn't change the underlying binary similarity. Apple compares compiled code, not just the surface UI. ## Common questions **Can you appeal a 4.3(a) rejection?** A 4.3(a) appeal requires concrete evidence of uniqueness. In your response: (1) Acknowledge the concern respectfully, (2) List specific features unique to your app with screenshots, (3) Explain your custom codebase — mention the language, frameworks, and original architecture, (4) If you used a template as a starting point, explain how much was rewritten and what's original, (5) Provide a comparison table showing differences from the similar apps Apple may have flagged. If you genuinely built everything from scratch and believe this is a false positive, say so clearly and offer to schedule a call or provide source code access. **How long does this typically take to fix?** Typical turnaround is 1-4 weeks (difficulty: hard). After resubmission, most re-reviews complete within 24-48 hours. --- *Machine-readable source: https://api.appstorereject.com/api/rejections/detail?slug=guideline-43a-design-spam-similar-binary-or-metadata*