Get it onto a phone.
Get it past review.
Most AI-built apps that reach the stores are rejected the first time, and almost always for the same reason. We work out which of the three routes your product actually needs, build the version that clears review, and hand you the pipeline that ships the next one.
- routes, priced honestly
- 3routes, priced honestly
- the guideline that rejects wrappers
- 4.2the guideline that rejects wrappers
- Play testing gate, started in week one
- 14 daysPlay testing gate, started in week one
- post-launch support
- 30 dayspost-launch support
Publish what you have, or rebuild it properly
Two different jobs that founders ask for in the same sentence. They differ by months and by an order of magnitude in cost, so they get separate pages and separate honest answers.
- Publish
Work out whether you need an app at all, then take the cheapest route that gets you there
There are three ways to get an AI-built web app onto a phone, and they differ by an order of magnitude in cost.
1 week to 12 weeks, depending on the answer - Publish
Get your app into the Apple App Store, past the review that rejects most of them
Apple rejects wrapped web apps under guideline 4.2, and that is the single most common outcome for an app built in Base44, Replit or Lovable and dropped into a WebView.
3–6 weeks to first submission - Publish
Ship to Google Play, including the 14-day testing gate nobody warns you about
Play is easier to publish to than the App Store and harder to plan around, because a new personal developer account has to run a closed test with a dozen real testers for fourteen continuous days before it can even apply for production.
4–7 weeks, driven by the testing window - Rebuild
Rebuild it in React Native and keep most of what you already have
Lovable, Bolt, v0 and most Base44 front ends are React. That is the whole argument for React Native: the component model, the state handling, the validation rules and every line of your API layer come across largely intact.
6–12 weeks depending on surface area - Rebuild
Rebuild it in Flutter when the interface is the product
Flutter draws every pixel itself, which is why an animation-heavy or heavily branded interface behaves identically on both platforms instead of nearly identically.
8–14 weeks depending on surface area
The cheapest route that actually gets you there
A rebuild is the most expensive of the three options and the one most founders are quoted. Sometimes it is right. We would rather establish that before you pay for it.
- 01
Route
Three ways onto a phone, an order of magnitude apart in cost.
- 02
Build
Whatever the route, the app gets real device capability - because that is what makes it worth installing, and what clears Apple's review.
- 03
Ship
Store accounts in your name, signing you control, a pipeline that submits from a tagged release, and a rollout that halts itself on a crash spike.
Not sure which route you need?
The decision review is free and ends with a written recommendation you keep - including the case for the cheaper option.