The App Store and Google Play received 60% more app submissions in Q1 2026 than they did in Q1 2025. On iOS alone, the surge was 80%. By April, the year-over-year jump for new releases had widened to 104%. None of those numbers are pandemic-style anomalies — they reflect a real, durable shift in who is building mobile apps and how fast they can ship.
The driver is well understood by now: AI-assisted coding tools have collapsed the cost of producing a working app from months to days. Claude Code, Cursor, Replit Agent, and a handful of similar systems have made the act of writing the binary almost incidental. What hasn't gotten cheaper is everything between a working binary and a paying user — and the apps that figure that out first will inherit a market that's getting noisier by the week.
This guide is for indie iOS and Android developers shipping into that environment. It's not a generic ASO post. It's a working set of tactics for the specific problem of being one of three million new apps trying to find an audience on stores that were never designed to discriminate at this scale.
What the submission boom is actually doing to discovery#
The first thing to understand is that "more apps" doesn't just mean more competition for the top spots. It means the discovery surface itself behaves differently.
Top-charts pages have always rewarded incumbents — apps with deep review counts and large user bases that compound visibility. With submission volume up 80% on iOS, those pages are even more locked in than before, because the new apps don't have the install velocity to crack into them. Search, by contrast, is more volatile: a long-tail search query that surfaced four results in 2024 might surface forty in 2026, and the keyword competition for any given term has roughly doubled.
The editorial surfaces — Today, Apps & Games, the curated story slots — are the only place where small apps still have meaningful upside. App Store Connect's editorial team and Google Play's curation team are both working through more pitches than they have time for, and they're filtering harder. The bar for an editorial pickup in 2026 is roughly where the bar for a "Best New App" pickup was in 2022.
What that adds up to: top-down distribution is harder, but quality-driven distribution still works. The apps winning right now are the ones treating the store listing itself as a product surface, not as an upload checkpoint.
Why most AI-built apps will lose#
Worth saying clearly because it's a tailwind for everyone reading this: most of the apps in the submission surge will fail discovery on their own merits.
The submissions data has a clear shape. A large fraction of new apps in 2026 are vibe-coded MVPs — built in a weekend, submitted with placeholder screenshots, copy generated by whatever model was cheapest, and a privacy manifest that doesn't quite match the binary. They get rejected on the first review, fixed with another round of AI patching, rejected again, and either limp through or get abandoned. Apple's reviewer team has been explicit about this: rejection rates climbed in 2026 specifically because of the volume of underbaked AI-built apps reaching first review.
The advantage available to a team that takes the metadata, screenshots, and reviewer experience seriously is bigger now than it was two years ago — not smaller. The ground floor of submission quality has dropped, and the work to clear it has gotten easier to outsource to tools.
The five surfaces that decide whether you get found#
Discovery in 2026 doesn't have one front door. It has five, and they all need to work for an indie launch to gain traction.
1. The screenshot stack#
Screenshots are the single most-viewed asset in any app's product page. They get glanced at in search results, scrolled through on the product page, and pulled into editorial layouts. A weak screenshot stack is the single most common reason a fundamentally good app fails to get installs, and it's the easiest thing to fix.
The 2026 standard for indie apps is roughly: five to eight screenshots per locale, the first three telling a coherent feature story without requiring the user to read body copy, localized text and device frames matching the user's region, and at least one screenshot showing real data rather than placeholder. The bar has moved — Apple's 2024 product pages tolerated minimalist screenshots, but the 2026 algorithm rewards information density much more aggressively.
For multi-locale apps, the manual cost of producing this stack is now the dominant pre-launch expense. If you're shipping to thirty locales, you're producing 150 to 240 screenshot variants every time the UI changes. This is the kind of work that should be automated — the team that built Stora's screenshot generator did so specifically because hand-producing localized screenshots was eating launches.
2. The metadata block#
The title, subtitle, keywords, and description aren't just SEO — they're the input the App Store and Play Store search algorithms use to rank your app against ten thousand others claiming the same category.
A few patterns are working in 2026 that weren't in 2024:
The subtitle slot has become more important on iOS. With more apps competing for the same head terms, the subtitle is the most movable lever for capturing long-tail intent. "[App Name] — calorie tracker for runners" outperforms "[App Name] — fitness made easy" by significant margins because the long-tail term is doing real ranking work.
Keyword stuffing in the description doesn't work and never has, but topical clustering does. A description that reads naturally while covering eight to twelve adjacent search terms ranks better than one that hits a single keyword aggressively.
Localized metadata isn't optional. Apps that ship in only English are leaving 60% of the App Store on the table, and the localization tooling has gotten cheap enough that there's no excuse. AI-translated metadata that's been reviewed by a fluent speaker outranks human-translated metadata that hasn't been updated since 2023.
3. The compliance posture#
This is the surface most indie teams underestimate.
A rejection on first review delays your launch by anywhere from three days to three weeks depending on the depth of the issue. Worse, a rejection that requires resubmission resets your editorial pipeline — if you'd been pitched to a curator, a rejection often means your slot moves to the next cycle.
The 2026 rejection landscape has specific traps:
- The AI consent disclosure rule (App Store Review Guideline 5.1.2(i)) catches apps that send any user data to external AI services without a named-provider consent screen.
- Privacy manifests are checked harder than before, and any mismatch between declared SDKs and actual SDKs flags the build automatically.
- The April 2026 SDK requirement (iOS 26 SDK or later) catches teams running stale build pipelines.
- Google's news/magazine self-declaration deadline (May 27, 2026) catches any app even adjacent to news content.
A pre-submission compliance pass is one of the highest-ROI activities an indie team can run. The cost of a five-minute automated check is trivial; the cost of a three-week rejection cycle is most of a launch.
4. The product page experience#
On both iOS and Android, the product page is now treated as a conversion funnel by the platforms themselves. Apple's Custom Product Pages and Google Play's store listing experiments let developers test variants of screenshots, descriptions, and previews against each other and route incoming traffic to the winner.
In 2026 these tools are table stakes, not advanced. Indie apps not running A/B tests on their product page are leaving conversion on the table — usually 15% to 40% lift between the worst and best variants of a hero screenshot.
The mistake to avoid: testing too many variables at once. The teams getting clean wins from product-page testing isolate one element at a time (hero screenshot, subtitle, app preview) and let each test run for at least 7,000 product-page visits before making a call.
5. The off-store push#
Stores were never the only acquisition channel, and in 2026 they're a smaller fraction of total installs than ever. The off-store surfaces that matter for indie discovery are: Twitter/X (still where iOS Twitter lives), Reddit (r/iOSProgramming, r/androiddev, category-specific subs), Hacker News (Show HN posts still drive meaningful traffic for technical apps), Product Hunt (less than it was, but not zero), and TikTok or YouTube Shorts (massive for consumer apps with visual hooks).
The pattern that's working: a single excellent demo video, posted natively to whichever surface fits the product, often does more for discovery than three months of paid acquisition. The video doesn't need production budget — it needs to show the app doing something interesting in under fifteen seconds.
A submission-week checklist for 2026#
For teams shipping into the 2026 environment, the high-leverage checklist looks like this:
- Screenshots regenerated for every locale, dated within the last 30 days. Stale screenshots from a previous UI version are the most common credibility leak.
- Subtitle and metadata reviewed against current search rankings for your top three keywords. If your subtitle hasn't moved in a year, it's almost certainly underperforming.
- Privacy manifest cross-checked against actual SDKs in the build. Any drift gets caught at upload now.
- AI consent screen present if any user data leaves the device for inference. This is the single fastest-growing rejection reason in 2026.
- At least one Custom Product Page variant configured. Even if you don't run a test, the variant gives you a fallback if your default page underperforms.
- A 15-second demo video ready to post natively to whichever social surface your audience uses. Editorial pickups now sometimes require a working video as part of the pitch.
- A pre-submission run through a compliance checker. The cost of catching an issue before review is roughly two orders of magnitude lower than catching it during review.
How Stora fits into this#
This guide is mostly about doing the discovery work — there's nothing here that requires any specific tool. But the work itself is heavy enough that doing it by hand for every release is what kills indie launches in practice.
Stora was built for the parts of this loop that compound across releases: regenerating localized screenshots when the UI changes, rewriting store listings against current platform metadata rules, running pre-submission compliance checks against the latest reviewer guidelines, and pushing the final build to App Store Connect and Play Console with the metadata and assets aligned. None of it replaces the strategic work — it just removes the manual cost of executing on it well.
The teams shipping fastest into the 2026 environment treat their submission pipeline the way they treat their CI: as something that should be automated, observable, and never the bottleneck. The apps that win discovery this year aren't the ones with the biggest budgets. They're the ones that can ship a polished, compliant, well-localized release every time the product gets better.
In a market with 60% more apps than last year, that's a real edge.