Glideep
Glide
Bubble
Shopify
Lovable
Base44You vibe-coded an app. Now ship it to the stores.
Lovable, Base44, Bolt, v0 — they all hand you the same thing: a web app at a URL. Apple and Google will not take a URL. Glideep turns it into real signed iOS and Android apps, usually in under two minutes. No code, no Mac.
Where every AI builder stops
It is not a flaw in the tool you used. It is a hard requirement of the app stores.
You describe the app
A prompt, a few iterations, and it works.
The builder ships a web app
Live at a URL. Real, working, shareable.
The stores refuse a URL
Apple wants a signed .ipa. Google wants a signed .aab.
You get both binaries
Signed, store-ready, from the same URL.
Those binaries need an icon set, a bundle identifier, permission declarations and a cryptographic signature tied to your developer account. No prompt produces one, because the builder has no native toolchain and no signing keys. That last mile is the whole job here.
From URL to both stores in 3 steps
Identical whether you built it with AI, no-code, or by hand.
Paste your app’s URL
A lovable.app subdomain, a custom domain, a Vercel deploy — whatever your builder gave you. Glideep reads it and pre-fills your name, icon and colours.
Add the native layer
Push, Face ID, native tab bar and drawer, splash screen, onboarding, camera and location. This is also what gets you past Apple’s review bar.
Build and ship
One click gives a signed .aab and .apk for Google Play, plus an .ipa pushed straight to TestFlight. Typically 1–2 minutes.
The rejection that catches almost everyone
App Store Review Guideline 4.2 — “minimum functionality”.
Gets rejected
- A web view and nothing else
- No capability the mobile browser lacks
- Reads as a bookmark with an icon
Gets approved
- Push notifications the browser cannot send
- Biometric lock — Face ID, Touch ID, fingerprint
- Native navigation, offline handling, camera, location
There is no trick to 4.2 — the fix is real functionality. Each item on the right is a toggle in the Glideep editor rather than code you have to write, which is exactly why they exist. Read the full 4.2 walkthrough →
Guides for specific tools
Any tool that gives you a public URL works. These have step-by-step pages.
Bolt.new, v0, Replit, Cursor or Claude? There is no separate guide because none is needed — the process is identical. Paste the deployed URL and build. See all supported platforms →
Questions
Can I publish a Lovable or Base44 app to the App Store?
Not directly from those tools. They output a web app at a URL, and neither store accepts a URL as a submission — they need a signed native binary. Glideep takes the URL and produces the .ipa and .aab the stores require.
Do I need a Mac?
No. iOS builds run on cloud macOS machines and the result is uploaded to TestFlight automatically. You do need an Apple Developer account ($99/year) to publish, and a Google Play Developer account ($25 one-time) for Android — those are the stores’ fees, not ours.
Will Apple reject it for being “just a website”?
That is guideline 4.2, and it is a genuine risk for any converted app that adds nothing native. Turning on push, biometric login and native navigation is what clears it. Full walkthrough here.
If I change my app in Lovable, do I have to resubmit?
No. The app loads your live URL, so content and design changes appear immediately for people who already installed it. Only native-layer changes — the app icon, the tab bar, push settings — need a new build.
Is the result a real native app or a wrapper?
It is a real signed native binary, and to be straight with you: your interface is still rendered from your web app. What makes it an app rather than a bookmark is the native layer around it — notifications, biometrics, native navigation, device APIs, offline handling. That distinction is exactly what the stores review against. More on how this works.
Ready to ship the app you already built?
Paste your URL and see it as a real app.
No credit card, no Mac, no code.