Guideline 4.2

Guideline 4.2 - Design: Minimal Content or Features

High RiskHardTypical Fix: 1-4 weeks0 Reports

Also known as:App has only one or two screens with limited interactivityApp is essentially a calculator, timer, or single-function tool with no additional valueApp launched with placeholder content or “coming soon” sectionsApp’s primary content is static text that doesn’t changeApp provides functionality that is already covered by built-in iOS appsApp is an MVP with too few features for Apple’s bar

Our Take

Apple rejected your app under Guideline 4.2 because it does not include enough content or features to qualify as a standalone App Store experience. Your app may function correctly, but Apple considers it too thin — it might be a single-purpose utility that could be a website, a feature within another app, or an app with placeholder content. This rejection signals that Apple does not believe your app provides sufficient value to justify a dedicated App Store listing.

Resolution Guide

Audit your app through Apple’s lens — Ask honestly: does this app provide more value than a website bookmark or a Shortcut? If not, you need to add features that justify a native app.

Add depth to your core feature — If your app does one thing, make it do that one thing exceptionally well with multiple layers:

History/favorites/bookmarks for past interactions

- Customization and settings (themes, units, preferences)

- Data visualization or statistics about usage

- Share/export functionality

Implement native iOS capabilities — Features that prove your app needs to be native:

Push notifications for timely updates

- Widgets (WidgetKit) for at-a-glance information

- Shortcuts/Siri integration for voice control

- Offline mode with local data persistence

- Live Activities for real-time status

Add content depth — If your app is content-based:

Ensure there is substantial initial content (not placeholder or “coming soon”)

- Add search, filtering, and categorization

- Include user-generated content features (favorites, notes, ratings)

Build complementary features — Think about what naturally extends your core concept:

A tip calculator app → add receipt splitting, payment tracking, restaurant history

- A countdown timer → add multiple timers, categories, widgets, reminders

- A unit converter → add favorites, history, currency rates, AR measurement

Remove placeholder content — Every section must be fully functional at review time. Remove any “coming soon” labels, greyed-out tabs, or empty states that suggest the app isn’t finished.

Write a clear review note — In your resubmission, explain the full feature set and use cases. Sometimes apps are richer than they appear at first glance, and a clear review note helps the reviewer understand the depth.

Example Rejection Email

From:Apple App Review Team

Subject:Guideline 4.2 - Design: Minimal Content or Features

Guideline 4.2 - Minimum Functionality We found that the usefulness of your app is limited by the minimal amount of content or features it includes. We encourage you to review your app concept and incorporate different content and features that are in compliance with the App Store Review Guidelines. We understand that there are no hard thresholds for what content is considered sufficient, but the App Store is intended for apps that provide a rich, engaging user experience. Next Steps: Consider how you can add additional features, content, and functionality to create a more robust app experience. Apps that are simple web clippings, content aggregators, or a collection of links may not be appropriate for the App Store.

Consider Appealing

Appeals rarely succeed for this rejection unless the reviewer genuinely missed features. If your app has hidden depth (e.g., features behind onboarding, or a demo account is needed), reply in Resolution Center with a detailed walkthrough video and explicit instructions for accessing all features. Otherwise, add more features and resubmit — arguing that your app is “sufficient” without changes almost never works.

Generate Appeal

Before & After

Before — Rejected

App structure that was rejected for minimal functionality:

Screen 1: Text input field + "Convert" button

Screen 2: Result display

No settings, no history, no offline mode

No widgets, no notifications, no Shortcuts

Total screens: 2

Total user interactions: type + tap button

After — Approved

Expanded app structure that passed review:

Tab 1 — Convert: Full converter with 50+ unit categories, favorites, swap button

Tab 2 — History: Searchable conversion history with date grouping

Tab 3 — Favorites: Pinned conversions for quick access

Settings: Theme selection, decimal precision, default units

Widget: Quick-convert widget showing favorited conversions

Shortcuts: "Convert X to Y" Siri Shortcut

Offline: All conversions work without internet

Share: Copy or share conversion results

Total screens: 8+ | Total features: 12+

What changed: The app went from a 2-screen utility to a full-featured conversion tool. Native iOS capabilities (widgets, Shortcuts, offline) prove it belongs as an app. History, favorites, and settings add depth that keeps users coming back.

Before — Rejected

// Entire app: one view with minimal interaction

struct ContentView: View {

@State private var input = ""

@State private var result = ""

var body: some View {

VStack {

TextField("Enter value", text: $input)

Button("Calculate") { result = calculate(input) }

Text(result)

}

After — Approved

// Rich app with tabs, history, widgets, and settings

@main

struct ConverterApp: App {

var body: some Scene {

WindowGroup {

TabView {

ConverterView()

.tabItem { Label("Convert", systemImage: "arrow.left.arrow.right") }

HistoryView()

.tabItem { Label("History", systemImage: "clock") }

FavoritesView()

.tabItem { Label("Favorites", systemImage: "star") }

SettingsView()

.tabItem { Label("Settings", systemImage: "gear") }

}

// Plus: WidgetBundle, AppIntents for Shortcuts, Core Data persistence

What changed: The single-view app was expanded into a tabbed application with four main sections. Adding History, Favorites, and Settings gives the app depth, while WidgetKit and AppIntents integration demonstrates native platform value that justifies an App Store listing.

Community Solutions · 0

More Guideline 4 (Design) rejections

View all Guideline 4 rejections

Guideline 4.2 - Design: Minimal Content or Features

Our Take

Resolution Guide

**Audit your app through Apple’s lens** — Ask honestly: does this app provide more value than a website bookmark or a Shortcut? If not, you need to add features that justify a native app.

**Add depth to your core feature** — If your app does one thing, make it do that one thing exceptionally well with multiple layers:

**Implement native iOS capabilities** — Features that prove your app needs to be native:

**Add content depth** — If your app is content-based:

**Build complementary features** — Think about what naturally extends your core concept:

**Remove placeholder content** — Every section must be fully functional at review time. Remove any “coming soon” labels, greyed-out tabs, or empty states that suggest the app isn’t finished.

**Write a clear review note** — In your resubmission, explain the full feature set and use cases. Sometimes apps are richer than they appear at first glance, and a clear review note helps the reviewer understand the depth.