App Store review

Apple reviews every app before it goes live. If your app wraps a website without adding native value, it will be rejected under guideline 4.2 (Minimum Functionality). Ruby Native is designed to pass this review.

#Why Ruby Native apps get approved

Apple rejects apps that are "repackaged websites." Ruby Native apps are not. Every app includes real native components that Apple expects to see:

• Native tab bar. Built with first-party iOS APIs, not a web element styled to look native.
• Push notifications. Real APNs integration, not a web push workaround.
• App icon and launch screen. Proper Xcode assets, not a web favicon.

These features are what separate a native app from a wrapped website in Apple's eyes. Ruby Native includes them by default, configured through YAML.

#Tips for a smooth review

Based on shipping 25+ apps through App Store review, here are the most common things to get right.

#Make your app feel complete

Apple tests your app as a new user. If reviewers hit a login wall with no way to explore, they may reject for "demo account required." Either provide a demo account in App Store Connect, or make sure unauthenticated users can see enough of the app to understand its value.

#Support account deletion

If your app supports account creation, Apple requires you to offer account deletion within the app. This has been enforced since June 2022. Add a "Delete account" option in your settings or profile page that removes the user's account and personal data. Your existing web-based account deletion page works inside the Ruby Native shell. No native-specific code needed.

#Be careful with in-app purchases

If your app sells digital goods or subscriptions, Apple requires their in-app purchase system and takes a cut. The payments guide covers the rules, the current cuts, and the companion-app path most Ruby Native apps take instead.

#Include required legal links

Every app needs a privacy policy link in two places: somewhere in your Rails app (a settings or profile page works well) and in the App Store Connect metadata. If you have terms of service, include those too. Apple checks for these during review.

#What Ruby Native handles for you

When you use cloud builds, Ruby Native takes care of the technical requirements that commonly trip up first-time submissions:

• Proper code signing and provisioning profiles
• Required Info.plist entries (camera, photo library permissions)
• Export compliance flag (ITSAppUsesNonExemptEncryption set to NO), so Apple won't ask about encryption on each submission
• App icon and launch screen assets in the correct formats
• A properly structured Xcode archive for App Store submission