Is My App Ready? See exactly what’s left before you publish

You open the app you just built, tap Settings, and land on a screen that says "Coming Soon." You tap a button on the profile page and nothing happens. Reasonable conclusion: something's broken.

It usually isn't. Those parts were never built — and nothing in your app told you that.

Today we're fixing the part that was actually wrong: the silence.

Meet "Is my app ready?"

There's a new button in your chat: Is my app ready? (or Is my site ready? for web projects). It gives you three things.

A score. "Your app is 76% ready," with your previous score next to it so you can see progress.

A list of what's missing. Each item named, with the file it lives in: which page was planned but not built, which buttons aren't wired to anything, where placeholder text is still sitting, whether the data people type actually gets saved.

Something you can do about each one. Build it, or remove it.

At the top of the list is one sentence: These are unfinished parts, not bugs. That sentence is the whole reason the feature exists.

Why your app has unfinished parts on purpose

The first build is deliberately an MVP. Even if you write a long, detailed prompt, Snapp builds the core of your main flow properly and leaves the rest as planned placeholders.

That's a real trade-off we chose: three screens built well beats twenty built badly. The mistake was never telling you which was which.

The score doesn't come from AI

This was the decision we thought hardest about, because asking the model would have been the easy path.

We don't ask it. The score comes from reading your app's actual source code — not a single model call. Three reasons that matters:

The same code always gives the same score. Ask a model "how ready is my app?" and you get a different number each time, and a number you can't trust.

It costs nothing. Open the report as often as you like.

It can't make things up. The model can't report a missing page as done, or a finished page as missing, because it has no say in the report at all.

Here's why that's not theoretical. While building this, we hit an app whose plan marked the Profile page as complete. The real code had seven buttons wired to nothing. Trusting the plan would have said "ready." Reading the code said "seven buttons do nothing when tapped."

Removing something is free

The most common item you'll see is a page that was planned but never built. Some of them you never asked for.

So every page gets two options: Build it or Remove from app.

Removing is completely free and uses no AI. The page is deleted, unregistered from navigation, dropped from the plan — and the buttons that led to it are cleaned up too. You shouldn't have to spend credits on a page you didn't want. Your score goes up immediately.

One safeguard: if the page is still used by another screen, the removal doesn't happen, and we tell you where it's used. Every removal also rebuilds and verifies your app first — if it doesn't compile, nothing changes.

What it checks

• Pages that were planned but never built, and screens nothing in your app links to
• Buttons with nothing behind them, and links pointing at pages that no longer exist
• Files that don't compile — the kind of syntax error that stops your app from opening at all
• Leftover sample content like lorem ipsum and you@example.com
• Whether data is really saved, and whether sign-in really signs anyone in
• Store requirements: app icon and privacy policy

The scoring is conditional: capabilities your app doesn't have can't hurt your score. No payment screen means no penalty for "payments not set up." We didn't want a simple counter app to look 40% finished.

Before you publish

If your readiness score is low when you list your app in the gallery, you'll now see a warning.

That's not just a nudge. Apps with unfinished pages get rejected by the App Store under "minimum functionality" all the time. Finding out before you submit is a lot cheaper than finding out after.

The warning doesn't block you. It's your call.

Where to find it

It's in the quick actions in your chat: Is my app ready? The report refreshes automatically after every change, and there's a re-check button if you want to force it.

Shipping an app is harder than starting one. At least now you can see what's left.