Menu

1 / 2

Shipping a Vibe-Coded App: 5 Things App Review Checks That Your AI Builder Didn't

DEV Community: ios·Sophie F A·about 21 hours ago
#okgvzZzN
#devtoios#devto#dev#account#privacy
Reading 0:00
15s threshold

TL;DR

4.2: a WebView around your web app is the classic rejection. Ship a native build.

4.8: Google/Facebook login for the main account means you also need an equivalent private-email option. Usually Sign in with Apple.

5.1.1(v) + Play policy: account creation means in-app account deletion. Google also wants a web link.

2.1: give the reviewer a working demo account, and keep the backend awake.

5.1.1(i) + Data safety: privacy policy in the listing and in the app. Declare what your SDKs collect.

1. "Beyond a repackaged website" (4.2)

Apple: your app "should include features, content, and UI that elevate it beyond a repackaged website." If your builder outputs a web app, wrapping it in a WebView is exactly what this catches. React Native/Expo output, push, offline handling and phone-first screens all help.

2. Social login needs a private option (4.8)

Using Google/Facebook/X/etc. for the primary account? You must also offer a login that only collects name + email and lets users hide their email.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.