The Complete Checklist for Publishing a WebView App to the Apple App Store

If you thought Google Play was strict about WebView apps, Apple is on another level. But getting approved isn't impossible — it just requires knowing exactly what Apple's reviewers look for.

The Key Guideline: 4.2 Minimum Functionality

Apple's Guideline 4.2 states:

This is the #1 reason WebView apps get rejected by Apple. Here's how to satisfy it.

Pre-Submission Checklist

Technical requirements

1. Xcode 16+ and latest iOS SDK: Build with the latest Xcode version targeting the current iOS SDK.
2. Universal Binary (arm64): All apps must support Apple Silicon natively.
3. App Transport Security: All network connections must use HTTPS. No exceptions for production apps.
4. IPv6 compatibility: Your app must work on IPv6-only networks. Apple tests this during review.
5. No private APIs: Only use public Apple frameworks. Private API usage = instant rejection.

Native features required for approval

Add at least 3-4 of these to differentiate your app from a browser bookmark:

• Push Notifications (APNs): The single most important feature. Shows your app has a reason to exist on the device.
• Native Navigation: Bottom tab bar, native back button behavior, swipe-to-go-back gesture.
• Biometric Authentication: Face ID / Touch ID support for login screens.
• Share Extension: Native share sheet integration for content sharing.
• Haptic Feedback: Subtle vibrations on interactive elements.
• Safe Area Handling: Proper support for the Dynamic Island, notch, and home indicator.
• Dark Mode Support: Respect the user's system-wide appearance setting.

App Store metadata

1. App icon (1024x1024): Must be a single, square PNG with no transparency or rounded corners (Apple rounds them automatically).
2. Screenshots: Required for 6.7" (iPhone 15 Pro Max) and 6.5" displays. iPad screenshots if your app supports iPad.
3. Privacy Policy URL: Mandatory. Must be accessible and describe all data collection.
4. App Privacy (Nutrition Labels): Declare all data types your app collects in App Store Connect.
5. Description: Accurate, no misleading claims. Mention that the app provides native features beyond the website.

Code signing and provisioning

1. Apple Developer Account ($99/year): Required for App Store distribution.
2. Distribution certificate: Create in Apple Developer portal or Xcode.
3. App Store provisioning profile: Tied to your Bundle ID.
4. Entitlements: Enable only the capabilities your app uses (Push, Associated Domains, etc.).

Common Apple Rejections and How to Fix Them

Rejection: Guideline 4.2 — Minimum Functionality

Apple says:

"We noticed that your app's content and experience are identical to the website, providing no additional value."

How to fix:

• Add push notifications — this alone often satisfies the requirement
• Implement native navigation (tab bar, swipe gestures)
• Add biometric login or persistent sessions
• In your App Review notes, explain what native features your app provides beyond the website

Rejection: Guideline 2.1 — App Completeness

Your app crashes or shows blank content during review. Apple tests on the latest iOS version and various device sizes.

How to fix:

• Test on iPhone SE (small screen) and iPhone 15 Pro Max (large screen)
• Test on the latest iOS version
• Ensure all web content loads over HTTPS
• Add an offline fallback screen for no-network scenarios

Rejection: Guideline 5.1.1 — Data Collection and Storage

Your app collects data you didn't declare, or your privacy policy is missing.

How to fix:

• Audit all analytics SDKs, crash reporters, and third-party services
• Update App Privacy labels in App Store Connect
• Ensure your privacy policy URL is valid and comprehensive

Pro Tips for Faster Approval

• Use App Review Notes: Write a clear note explaining your app's native features. Example: "This app provides push notifications via APNs, native tab navigation, Face ID authentication, and haptic feedback — features not available through Safari."
• Provide demo credentials: If your app requires login, give the reviewer a test account.
• Submit on Monday/Tuesday: Review times tend to be faster early in the week.
• Don't argue with the first rejection: Fix the issues and resubmit. If you believe the rejection was wrong, request a call with App Review by clicking "Contact the App Review team."

FAQ

How long does Apple App Review take?

Average review time is 24-48 hours. First submissions for new apps can take up to a week. Expedited reviews are available for critical bug fixes.

Can I build an iOS app without a Mac?

Yes. Cloud build services like Code2Native run Xcode on remote Mac hardware. You still need an Apple Developer Account ($99/year) for code signing, but you don't need to own a Mac.

Will Apple approve a Shopify/WordPress wrapper app?

Yes, if it provides native features. Many Shopify/WordPress apps are live on the App Store built with WebView technology. The key is push notifications + native navigation + proper branding.