Mobile App Growth Blog

Every ASO framework assumes you already have rankings, conversion rates and A/B test results to optimise against. A brand-new app has none of them. This guide covers only the data-free stage: how to build a keyword set, model the right competitors, and make the listing decisions iOS gives you no way to test yet — plus what Play does let you experiment on before launch, and how long you will wait for the rest.

Your app name is the shortest, most permanent and most contested piece of metadata you will ever write. Thirty characters on each store, a trademark exposure you cannot undo cheaply, and no way to A/B test it once you are live. Here is how to choose one properly.

Your screenshot set is the largest surface on the product page and the one place you get to argue for the install rather than describe it. This is how we design sets that survive the two-second scan: what the first panel must do, how to sequence the rest, which caption styles work, and the size, format and content rules on both stores — including the Play restrictions that quietly make an iOS set non-compliant on Android.

Every ASO guide tells you review velocity is a ranking factor. Almost none tells you how to earn reviews without doing something both stores prohibit — starting with the tactic most apps are quietly using right now.

Both stores document their own submission flow well. What neither documents is the sequence — which decisions are permanent, which paperwork has a month-long lead time, and which step is the one that actually delays first launches.

A rejection is a paragraph of guideline text and no explanation of what to change. Six guidelines account for most first-submission rejections, and every one of them is avoidable before you submit — if you know what the reviewer is actually looking at.

If you opened a personal Play Console account after November 2023, you cannot publish to production until 12 testers have stayed opted in for 14 straight days. Most developers lose weeks to this rule because nobody explains how the clock actually works — or why buying testers is the fastest way to lose the account.

A fast-growing Indian discount-broking app was buying installs efficiently but bleeding them in the account-opening funnel — only 36% of the users who started KYC finished it, and just 8% of installs ever placed a trade. Over five months we rebuilt the KYC funnel, the first-trade experience, and the early-retention loop: KYC completion climbed from 36% to 59%, install-to-first-trade doubled from 8% to 17%, D30 retention rose from 12% to 20%, and CAC payback fell from 14 months to 8. Here is the full activation playbook.

An Indian bill-payment and recharge app could acquire users at scale but could not keep them — most paid once and lapsed. Acquisition was never the problem; repeat usage was. Over four months we rebuilt the lifecycle: bill-due reminders across push and WhatsApp, a UPI Autopay mandate-adoption programme, rewards and streaks for repeat payers, and behavioural 30/60/90-day win-back sequences. Month-1 repeat-payment rate climbed from 27% to 43%, D30 retention from 9% to 17%, UPI Autopay adoption from 11% to 29%, monthly churn fell roughly 30%, and reactivation campaigns recovered about 22% of lapsed users. Here is the full retention playbook.

A professional networking app had installs but almost no activated users — most people never completed a profile or formed enough connections to reach the value moment, so retention and word-of-mouth were both weak. Over six months we redefined the activation metric, rebuilt onboarding around it, and engineered a double-sided invite loop. Profile completion went 41% to 67%, install-to-5-connections 22% to 44%, D7 retention 14% to 27%, and the k-factor 0.3 to 0.7. Here is the full activation-and-viral-loop playbook.

A B2B invoicing and GST-billing app for small businesses had no shortage of trials — SMB owners installed and started one every day. The problem was downstream: most never created their first invoice, and only 4% ever paid. In five months we rebuilt the product-led-growth motion around first value — compressing time-to-first-invoice from ~3 days to under 20 minutes, lifting activation from 38% to 64%, and nearly tripling free-trial-to-paid from 4% to 11%. Here is the full activation playbook.

A digital lending app for small and medium businesses was paying a fortune to acquire borrowers — and most of them never finished the application. Install-to-application sat at 14% and application-start-to-submitted at just 31%, so the blended cost-per-funded-loan was unsustainable. Over six months we rebuilt the loan-application funnel, fixed the document-upload and KYC drop-off, launched a WhatsApp win-back for abandoned applications, and re-pointed every rupee of media at the funded-loan event. Cost-per-funded-loan fell ~38%. Here is the full playbook.

A linkable benchmark for India's mobile app market in 2026 — download scale, smartphone user base, the UPI backdrop, the Android vs iOS split, the high-downloads low-ARPU reality, and which verticals are actually growing. Every figure attributed, framed as reported and directional.

StoreKit 2 and Google Play Billing handle the purchase on-device for free — but server-side validation, cross-platform entitlements, subscription state and paywall testing are still yours to build. Here is an honest build-versus-buy breakdown of native IAP versus RevenueCat (and peers like Adapty), with the trade-offs that actually decide it.

The app monetisation tooling market looks crowded until you split it into three jobs — subscription and IAP infrastructure, paywall experimentation, and ad mediation. This vendor-neutral comparison maps the real platforms in each category, names a free-or-cheap starter for every one, and tells you which to pick for your app type and stage — with the India angle on UPI billing and low-ARPU hybrid models built in.

The right messaging tool is not the most powerful one — it is the one that matches your stage and budget. This vendor-neutral guide compares raw push delivery (FCM, APNs), all-in-one push services like OneSignal, full CRM suites like CleverTap, MoEngage, Braze and WebEngage, and the India must-have — WhatsApp Business API — so you can start free, spend nothing until you need to, and graduate deliberately.

Most teams conflate two completely different jobs: testing your store listing (icon, screenshots) and testing what happens inside the app (features, flows, paywalls). They need different tools. Here is a vendor-neutral map of which tool to reach for, what is free, and the iOS-versus-Android gap that changes everything.

Notion crossed tens of millions of users and a multi-billion-dollar valuation without buying its way there — it grew through product-led, bottoms-up adoption, a template gallery that ran as a content engine, and a community that compounded the word of mouth. This is a teardown of that playbook, with the transferable lesson for app teams at the end of every section.

Spotify grew from a regional European startup into a service with hundreds of millions of monthly active users and hundreds of millions of paying subscribers — and it did it with a compounding system, not a single hack. This is a teardown of the freemium funnel, the personalisation engine, the Wrapped content loop and the localisation playbook, with the transferable lesson for your own app at the end of every section.

Headspace turned an abstract, intimidating behaviour — meditation — into a daily habit for tens of millions of people, and built a large paying subscriber base on top of it. This is a teardown of the onboarding, habit mechanics, subscription balance, brand and workplace-distribution system that did it, with the transferable lesson at the end of every section.

Instagram reportedly reached its first million users within weeks of launch and went on to surpass a billion — and it did it without a clever paid-acquisition trick. This is a teardown of the sharp single use-case, the frictionless cross-posting, the follow-driven content and notification loop, the fast simple product, and the later Stories expansion that compounded it all, with the transferable lesson at the end of every section.

A web-to-app funnel routes the cheap, high-intent traffic you already win on the web — SEO, content, ads — into app installs and in-app revenue, instead of letting it die on a mobile site. This guide covers the mechanics (Smart App Banners, deferred deep links, QR, SMS), when web beats sending people straight to the store, why web purchase flows are growing, and how to measure the whole thing.

The app growth tooling landscape is overwhelming until you organise it by funnel stage. This is the vendor-neutral, free-first map of every layer — ASO, user acquisition, attribution, analytics, engagement and monetisation — with a starter stack you can run for almost nothing and a clear signal for when each layer is worth paying to upgrade.

Deep links route a tap straight to the right screen inside your app, and deferred deep links carry that destination through an install. This guide explains how both work, how to set up iOS Universal Links and Android App Links correctly, and how to stop links silently falling back to the browser.