FOR PEOPLE BUILDING AN APP

The App
Readiness
Check

Six checks before you build, launch or rebuild a mobile or web app, now with an AI lens. Drawn from Apple's own review data, published retention benchmarks and the apps we ship for clients.

Choose the one number your app should move
Make your app easy for AI assistants to explain
Get through store review without a rejection
Plan the first 30 days after launch

Where should we send it?

A short form. Download the guide straight away, and we'll email you a copy too.

We only use your details to send the guide. See our privacy policy.

What the data says about apps

Four published figures that explain why a readiness check pays off before you write a line of code.

23%

of App Store submissions were rejected in 2025: 2.09 million of 9.1 million

Apple App Store Transparency Report 2025
65%

of those rejected submissions cited the Performance section of the review guidelines

Apple App Store Transparency Report 2025
387,087

rejected submissions were later approved, after the issues were addressed

Apple App Store Transparency Report 2025
<5%

of users are still active after 30 days in most app categories

AppsFlyer benchmarks, via Braze

Four things to know before you build

Each one turns into a decision you can make before the first screen is designed.

DISCOVERY

AI assistants are a new place people look

People ask assistants what to use, as well as searching and browsing the stores. An assistant can only recommend an app it clearly understands. The check: can it explain yours in one sentence?

REVIEW

Store review is the first test

Nearly one in four submissions was rejected last year, and most rejections touched performance. The check: is the app stable, complete and compliant before you submit?

RETENTION

Most users are gone within a month

In most categories fewer than five in a hundred users remain after 30 days. The check: which single number should move, and does the first session show it?

BUILD

A prototype is not a product

AI tools can produce a working app in days. The check: what is still a draft, who keeps it secure, and who maintains it after launch?

What is inside

Plain language, written for the person who owns the app decision rather than the code.

Three formats in one download

  • A launch-readiness checklist covering build, AI readiness, store review and security
  • A one-page scope worksheet for the first version
  • Questions to ask any development partner before you sign
Pick the one number the app should move, and how you will measure it
Decide what goes into version one and what can wait
Make the app easy for AI assistants to explain, with a one-sentence test and a way to try it
Prepare for store review: stability, privacy declarations and listing details
Plan the first 30 days: onboarding, notifications and reasons to return
Keep it safe after launch: patching, hosting, backups and ownership

Ready to build an app people find and keep?

Take the check before you brief a developer. It takes an afternoon.

Get the guide →