The App Growth Audit is a free tool from ApsteQ. Paste your App Store or Google Play link, answer a few multiple choice questions, and get a store page score out of 100, the stage where you lose the most users, and your top three fixes in order. It takes about three minutes and needs no call.
The report is about your app, not a generic checklist. Every number comes from your public store listing or from your own answers. If your app is live, you get:
If your app is not in the stores yet, choose the building path. You get a launch readiness score out of 100 (labelled as our estimate), how complex version one is (simple, standard or complex), your next three steps for your stage, and watch-outs for each feature you pick, such as store billing fees, Sign in with Apple, moderation for chat and uploads, push permission and third-party API terms. The build path does not give prices.
The checks are limited to what any visitor can see on your listing. Each one is scored green, amber or red against our thresholds.
| Check | Green | Amber | Red |
|---|---|---|---|
| Title says what the app does | Has a descriptor, such as Name: what it does | Brand name only | - |
| Screenshot slots (10 on iOS, 8 on Play) | All used | 5 or more used | Fewer than 5 |
| Star rating | 4.5 or higher | 4.0 to 4.4 | Under 4.0, or no ratings |
| Number of ratings | 500 or more | 50 to 499 | Under 50 |
| Last updated | Within 30 days | 31 to 90 days | Over 90 days |
| Download size (iOS) | 100 MB or less | Over 100 MB | - |
These thresholds are ApsteQ's own scoring rules, not store requirements. Languages on iOS are shown but not scored, and the first 130 characters of your description are shown for you to judge.
We chose these checks because they are visible, comparable between apps and fixable without code. A title that says only the brand name tells the store and the visitor little about what the app does. A low count of ratings reads as untested to a stranger. A listing that has not been updated for months can signal an app nobody is maintaining.
The four areas are the store page (title, screenshots, the first lines of the description, size), social proof (rating and volume), signs of life (update recency and languages) and your funnel (the stage that leaks most).
A good app audit checks the four stages a user passes through: finding the app, deciding to install from the store page, reaching value in the first session, and paying. Start with the store page, because it is public and quick to judge. Look for a title that says what the app does, all screenshot slots used, a healthy star rating with enough ratings behind it, and a recent update. Then check what the store page cannot show you: onboarding completion, retention in the first week, and conversion to paid. The point of an audit is not a long list of issues. It is to find the one stage that loses the most users and fix that first, because improving a stage that is not the bottleneck changes little. Our free audit reads the public store page, takes your answers about the other stages, and ranks the fixes in order.
For a longer walk-through, see our ASO checklist and our guide to App Store Optimization.
Both stores cap how much you can say, so every character and slot counts. On the App Store, the app name is limited to 30 characters, the subtitle to 30, and you can upload up to 10 screenshots per device size. On Google Play, the app name is also limited to 30 characters, the short description to 80, and you can add up to 8 screenshots for each supported device type. Both stores allow a full description of up to 4,000 characters. Apple's review guidelines add that screenshots should show the app in use, not merely title art, a login page or a splash screen, and that metadata should not include prices or unverifiable product claims. These limits are why a listing audit looks at the title descriptor and at how many screenshot slots are used. Unused slots are free space to explain what the app does.
| Listing element | Apple App Store | Google Play |
|---|---|---|
| App name | 2 to 30 characters | 30 characters |
| Subtitle or short description | Subtitle: up to 30 characters | Short description: up to 80 characters |
| Screenshots | 1 minimum, up to 10 per device size | Up to 8 per device type |
| Full description | Up to 4,000 characters | Up to 4,000 characters |
Sources: Apple, App information, Apple, Screenshot specifications, Apple, Platform version information, Google Play, Create your store listing and Google Play, Add preview assets.
The metadata rules are in the App Store Review Guidelines, sections 2.3.3 (screenshots) and 2.3.7 (name and subtitle).
Conversion rate here means the share of people who view your store page and then install. AppTweak reported that, across categories in the US in 2025, the average was 8.56% on the App Store and 16.15% on Google Play. Treat these as rough reference points, not targets. The rate varies widely by category, by traffic source and by how a company counts a page view: a branded search converts far better than a cold ad tap. The App Growth Audit does not measure your conversion rate, because it only reads the public listing and cannot see your store console. Check your own figure in App Store Connect or Google Play Console, then use the checks above to look for likely causes if you are below your category. Screenshots, the title and the volume of ratings are the usual levers.
| Reference point | Figure | Source |
|---|---|---|
| Average product page conversion, US App Store, 2025 | 8.56% | AppTweak |
| Average product page conversion, US Google Play, 2025 | 16.15% | |
| Android vitals bad behavior threshold, user-perceived crash rate (overall) | 1.09% | Android Developers |
| Android vitals bad behavior threshold, user-perceived ANR rate (overall) | 0.47% |
The Android vitals figures are included because they sit next to conversion in your Play Console. The audit itself does not read them.
The audit reads your public store listing and the answers you give. It does not log in to App Store Connect or Google Play Console, so it cannot see your real conversion rate, crash rate, retention curves or revenue. It does not edit your listing and it does not test your app's code. That boundary matters, because some problems only show up in your console. Google, for example, publishes bad behavior thresholds in Android vitals: an overall user-perceived crash rate of 1.09% and an ANR rate of 0.47%, above which Play may reduce your visibility. Check those numbers in your own console. Where your answers point to a weak spot in first use or in monetisation, the report names that stage as the one to look at next, and a strategy call can go deeper with console access.
Most apps we look at lose the most users at one stage, not everywhere. When that stage is the store page, the fixes are cheap and fast, and they make every later dollar of marketing work harder. When it is first use or payment, ads only make the problem more expensive.
Ratings volume and screenshot one come up most often. A listing with few ratings and a first screenshot that shows the interface rather than the result a user gets is asking a stranger to take a risk. We would rather fix that before paying for traffic.
The audit follows the same order. It ranks the store page first because it is the cheapest to fix and the easiest to check from outside.
The audit is built by ApsteQ. We were founded in 2015 and have worked on 300+ apps and brands, driven 52M+ installs and managed $2.5M+ in ad spend. See what that looks like in our case studies, including JFIT Connect, LunarLinc, EarningsCall and Enjoy Movies Your Way.
If the audit shows a store page problem, our App Store Optimization service fixes it. If you are still building, see App Development. For more tools, browse our store listing checker and ASO score tools, or read about screenshot optimization and rating optimization.
Yes. There is no card, no trial and no charge. You see the full report on screen. If your answers suggest we could help, we offer a call at the end, and you can ignore it.
No. The report appears without a call. You do enter your name, email and phone number before it is shown, and we email you a copy. Any call is optional.
We email you a copy of your report and add you to our weekly app growth email. You can unsubscribe from the email in one click. We do not need access to your accounts or your app.
No. It only reads your public store page, the same page any visitor sees. It does not log in to App Store Connect or Google Play Console, and it cannot edit your listing.
Either one. After the first link, the audit asks for the other store, and each store is checked and scored separately. If your app is not in the stores yet, choose the building path instead.
ApsteQ, an app marketing and development company founded in 2015. We have worked on 300+ apps and brands, driven 52M+ installs and managed $2.5M+ in ad spend. The audit applies the store page checks we run on client apps.
Paste your store link, answer a few taps and see your score, your leak and your first three fixes.