Mobile App Growth Blog

A verified directory of what actually exists for mobile development in Claude Code — skills, plugins and MCP servers — with the corrections that most published lists get wrong and the context cost of installing them all.

Most problems in agent-driven Expo work are setup problems. This is the scaffold to start from, the AGENTS.md template that carries your rules into every session, the eas.json profiles you need, and which MCP servers are worth their context cost.

Expo Go is a preview app, not your app. The moment you add a native module it stops being useful, and that transition catches most projects in week six rather than day two. Here is what actually changes and why to cross it deliberately.

An agent that cannot run your app is guessing. These are the MCP servers that let it build, launch, screenshot and read logs from a simulator or a real device, what each one is actually for, and why to start with one loop rather than five servers.

The question is not which framework is best, but which one an agent writes well. Those are different questions with different answers, and the deciding factors are training coverage, documentation shape and how loudly the framework fails.

Point an agent at Apple’s Human Interface Guidelines and it gets almost nothing back — the page renders client-side. There is a JSON mirror that returns the real content, and this is the verified URL list, plus the Android routing that actually resolves.

Design-to-code demos look convincing and production results rarely match them. This is what Figma MCP actually emits for each mobile platform, the two things that genuinely improve output, and the problem no converter solves.

The design system that produces the best agent output is not the fastest one. It is the one the agent can read. Here is why that is the deciding factor, and how seven mobile options rank against it.

Your rejection notice cites a guideline number and explains almost nothing. This is what Apple actually publishes, which guidelines genuinely catch agent-built apps, and why the statistic everyone quotes about AI apps does not exist.

A reviewer with no memory of writing the code catches what the author cannot. This is how to run one on mobile pull requests, the runner cost trap that surprises people, and an honest account of what it does not catch.

Most growth MCP servers are read-only, and the ones that write are the ones worth being careful with. This maps what an agent can actually do across ads, attribution, analytics, paywalls and lifecycle messaging.

Building a mobile app got very cheap in the last eighteen months. Shipping one did not. This is the ordered path from idea to store listing with Claude Code, including the five cliffs that stop most projects and the compliance work that decides whether you ship at all.

Coding agents write mobile layouts that look right in a screenshot and fail on a real device. The failures are consistent and enumerable: safe-area insets, Dynamic Type, touch-target size and the states nobody screenshots. Here is the full list, with a skill file that encodes the fixes.

Four store rules landing across 2026 catch exactly the app a coding agent builds by default. Each one blocks updates rather than launches, which is why teams meet them late. Here are the dates, what each blocks, and the order to handle them in.

An .ipa is a zip file, and anything you bundled into it ships to every device that installs your app. This is what actually leaks in vibecoded mobile apps, why the widely-blamed anon key is not the problem, and the eight things to fix.

Prompt-to-app builders are genuinely good at the first afternoon and consistently bad at the six weeks that follow. This is what each one does well, the wall every one of them hits, and why source export is the single feature that decides how the story ends.

Ask any coding agent for a landing page and you recognise the output before you finish scrolling. The fix is not a better prompt — it is persistent design context. This guide reviews every Claude Code design plugin, skill and MCP server worth your time, and ends with a skill file you can install in one command.

There is no universally correct weekly or monthly app update schedule. This guide gives founders a risk-based release system: how to separate hotfixes, maintenance and product releases, when to hold a build, and which signals should change the calendar.

AdMob mediation can improve competition for an impression, but more networks do not automatically create more profit. This indie-app guide covers architecture, partner selection, SDK risk, A/B testing, reporting and the operating controls that protect retention.

Deleting an app account does not automatically cancel an Apple or Google subscription. This implementation guide separates identity, personal data, billing and entitlement state so users receive a clear, compliant and testable deletion flow.

Low traffic does not prevent learning; it prevents small-effect A/B tests from resolving quickly. This guide shows indie teams how to select high-information tests, size decisions, combine behavioural and qualitative evidence, and report uncertainty honestly.

User-generated content turns moderation into a continuous product operation, not a policy page. This guide maps preventive controls, reporting, queues, severity tiers, enforcement, appeals, evidence retention, staffing and App Store or Play review readiness.

A healthy global crash rate can hide a severe defect on one popular device family. This runbook shows how to move from Play Console’s device breakdown to variant-aware reproduction, evidence-based mitigation, verified fixes and safe rollout.

A referral programme becomes a payment system the moment rewards have value. This guide shows founders how to model abuse, validate qualifying events, use device integrity safely, control reward release, investigate clusters and protect legitimate advocates.

Reviews are public product evidence; support tickets contain deeper diagnostic context. This playbook unifies both into a privacy-aware operating loop for incident detection, helpful replies, theme analysis, roadmap evidence and release verification.

The first 1,000 users require a bridge between hand-recruited learning and repeatable distribution. This guide gives founders a 12-week channel sequence, activation gates, weekly scorecard, ethical launch tactics and evidence-based transition to paid growth.

A founder-friendly control sheet for the app behaviours most likely to create privacy, billing, account-deletion, UGC, permission, SDK, and review problems on Apple and Google Play.

Play Console is more than the upload screen. This field guide shows founders how to use its overlooked acquisition, testing, quality, release, policy, and financial controls as one operating system.

App SEO is not a trick for indexing screens inside a binary. It is a web demand, content, technical-routing, store-conversion and measurement system that turns qualified searches into installs or app opens.

Most App campaign bid strategy arguments are really eligibility arguments. Google publishes a conversion-volume requirement for tROAS, a warning that small budgets on Maximize conversions may get no conversions at all, and an explicit caution against bidding on more than one in-app action. Read in order, those three rules decide the strategy for you.

Someone on your team wants to know whether shaving megabytes off the build will move installs, and every number they can find online is a vendor blog quoting another vendor blog. Google does document the relationship, in plain language, on pages that disagree with each other about the actual limit. Here is what the primary sources say, what they do not say, and which Play Console metrics tell you whether size is costing you anything.

Most App campaigns are lost in the setup screen, not in the auction. Google publishes the budget-to-bid ratios, the conversion-volume floor and the asset counts the system needs, and almost every failing launch has broken one of them before a single impression served. This is the launch sequence in the order the documentation supports it.

You changed the title, the screenshots and the description, and three weeks later nothing has obviously happened. Part of that is real: the stores publish two timing anchors worth planning around, a 28-day quality window on Google Play and a 90-day test length on the App Store. The rest of the timeline is undocumented, and most of the confident week-by-week figures circulating about ASO are invented.

You shipped an update, the crash rate moved, and now you are trying to work out what you can actually take back. The two stores answer that question very differently: Apple gives you a fixed seven-day ramp you can pause, Google gives you a percentage dial and a halt that works even after full rollout. Neither one removes a bad version from a phone that already has it.

Your ad platform claims one install number, Play Console shows another, and App Analytics shows a third. None of them are lying. Each store counts a different event, at a different moment, for a different population of users, and once you know which event each report is actually counting the three numbers stop contradicting each other.

Your app is live, the listing looks fine, and it appears nowhere. "Not ranking" is not one problem — it is at least six, and they fail in a fixed order. Work the fault tree from indexing upward and most teams find the answer two branches before they reach keyword strategy.

Your cost per install has drifted upward for three weeks and the campaign settings have not changed. That combination has a small number of documented causes, and most teams check them in the wrong order — starting with bids, which is the one lever most likely to make the problem worse. This is the fault tree we work through instead.

Most Firebase event plans are a list of screens somebody walked through, which is why nobody opens the dashboard six months later. A plan that survives contact with a real product starts from the decision each event is meant to settle, not from the interface. Here is the four-column template we use, and the documented limits that quietly decide what you are allowed to put in it.

You changed a value in the Firebase console, the console says published, and a large share of your users are still on the old behaviour. Nothing is broken. Remote Config has a value priority order, a client cache and an activation step, and each of them is doing exactly what it is documented to do. This is how to read the mechanism, and why a config change still deserves the discipline of a release.

You shipped a bad build, hit halt rollout, and the number of affected users did not fall. That is not a bug — halting a staged rollout and halting a fully rolled-out release are two different operations with two different outcomes, and neither one is a rollback. Here is what each control actually does, why a track’s first release cannot be halted, and how managed publishing changes the shape of the problem before it starts.

Both stores report something that looks like uninstalls, and neither reports the thing most teams think they are asking for. Apple counts Deletions from opted-in devices and hides small numbers on purpose; Google Play counts a user as lost after thirty days of silence, whether or not anything was uninstalled. This is what each number actually counts, and how far you can get towards identifying an individual leaver.

You call the review API, the code path runs, and no dialog appears. On both stores that is a documented outcome rather than a bug: Play enforces a quota it will not disclose, Apple caps the prompt and lets users switch it off entirely, and neither API reports back whether anything was shown. Here is the fault tree, in the order worth checking.

Your build is finished, uploaded and going nowhere. Most Play Console blocks are not code problems at all — they are unanswered declarations, and each one has a different owner, a different review queue and a different penalty for getting it wrong. This is the fault tree, taken from Google's own documentation.

Your retention curve is falling and none of your product experiments move it. That is often because the churn is not a product problem at all — it is a crash concentrated on one handset, an ANR nobody reports, a cold start over five seconds, or a download too large to finish. Google documents thresholds for all four, and they are stricter than most teams assume.

Most teams shut an app down by simply stopping work on it, which is the one option neither store lets you take quietly. Apple states plainly that an app you no longer actively support will be removed, and Google Play will not let you delete a monetised app at all once it has installs. This is the sequence that ends an app without stranding the people still paying you.

Two questions get merged into one decision and both get answered wrong. Apple will not let you gate a first launch behind a login unless your app genuinely has account-based features, and Google Play tells you outright that its purchase notifications do not carry complete information about the purchase. One of these questions is a policy constraint; the other is an architecture constraint, and they resolve separately.

You budgeted for 15% and your Play Console statement says 30%. The lower tier is not automatic — it requires an enrolment most teams never completed, enrolment most teams never completed, and within an account group the threshold is pooled across every developer account you own. Alternative billing in India reduces the fee by four percentage points, but only for developers who build and certify a second payment stack.

Every paywall review turns into an argument about whether to add a third plan, and nobody in the room has evidence either way. The store documentation will not tell you the optimal number, but it does define what a plan is, how many you may create, and what each extra one costs you in price-change flexibility. That is enough to decide.

Every MVP guide tells you to cut scope until only one feature survives. Neither store has read that guide. Apple and Google both publish a floor below which an app is not a product, and version one has to clear it before a single user sees the listing.

Every stack comparison you have read is a benchmark argument, and benchmarks do not survive contact with your build flags. The decision that actually matters is which documented store constraints your app will run into: download size caps, the startup thresholds Android vitals treats as excessive, how a crash gets attributed, and whether the SDKs your growth stack depends on exist for your framework. Those are all published, and they decide more than framework speed does.

Your cancellation count and your churn count disagree, and both stores are technically right. Google Play fires one notification for voluntary and involuntary cancellation alike, while Apple splits the same event across a renewal-status change and a later expiry with a subtype attached. Until you read the payloads the way the documentation defines them, every win-back campaign you build is aimed at the wrong cohort.

Your active subscriber count fell but almost nobody pressed cancel. That gap is involuntary churn — cards that expired, banks that declined, wallets that ran dry — and both stores run a long, documented recovery machine to win those payments back. Most of the revenue is lost not by the store giving up but by the app revoking access at the wrong moment.

Most idea validation tests whether people want the thing and whether you can build it. It rarely tests the third condition, which is whether the stores will distribute it at all. Apple and Google both publish the rules that decide that, and reading them before you write code is the cheapest validation step available.

Half the app SEO advice online describes a system Google no longer runs. Firebase App Indexing is no longer the recommended way of indexing content for Google Search App, and the Search App on Android no longer uses locally indexed content. What replaced it is narrower, better documented, and mostly a web problem with an app-shaped destination.

Most expansion decisions are made on market size, which is the one input that tells you nothing about whether the market will pay you back. The store mechanics make it worse: Google Play targets releases by the country a user registered their account in, not where they are standing, while your ad platform targets something else entirely. This is the sequencing framework we apply to a client's own numbers, with no invented benchmarks in it.

Someone typing your competitor name plus the word "alternative" has already decided to switch. That search cannot be answered by your store listing, because store metadata policy restricts what you may say about other brands. It can be answered by a page on your own site — and Google publishes enough documentation to tell you which version of that page survives and which one gets classified as spam.

Most founders ask this as a marketing question and get a marketing answer. The useful answer is mechanical: a developer website is a documented precondition for AdMob to verify your app-ads.txt file, and a domain you control is the only place the two stores will look for the files that make deep links open your app. Neither store makes a website mandatory to publish, which is exactly why the requirement gets discovered late.

Someone in Jakarta sees your listing in Indonesian and you never wrote a word of Indonesian. That is Google Play doing two different things under one word, and knowing which one is running on your listing decides whether you have a localisation problem or not. The text is the easy part; the screenshots, the in-app strings and the support inbox are where the money leaks.

Most teams find custom store listings after they have already built a workaround for the problem custom listings solve. The feature lets you show a different name, icon, description and screenshots to a targeted slice of Play traffic, and Google documents both the ceiling and the constraints. The constraints are where the plans usually break.

Localisation is sold as one decision and priced as one invoice, but the stores treat the listing and the binary as two entirely separate systems with two separate fallbacks. Google Play will now translate your app strings at no cost while charging for listing translation; Apple charges for neither and supplies neither. Knowing which half of the work each store does for you is what decides where the money goes.

You have picked the market. What breaks next is almost never the choice — it is the order. Pricing that was set before the tax position was settled, a listing translated before anyone checked the store supports the language, availability flipped on before a local payment method existed. Some of those steps are reversible and some are not, and the store documentation tells you which.

A creator posts, your installs rise, and nothing in your dashboard connects the two. The gap is almost never the creator — it is that the link, the listing and the redemption path were designed after the deal was signed instead of before it. This is the mechanics side: what the stores actually hand back to you, and what no amount of briefing can recover.

Uninstall rate is the retention metric everyone quotes and almost nobody defines. Google Play folds 30 days of device inactivity into the same number as a genuine uninstall, Firebase counts a different population entirely, and on iOS the metric you think you are reading does not exist. Here is what each source actually measures, and the one Play threshold that carries a documented consequence.

Every list of the cheapest CPI countries traces back to another list, and none of them trace back to a source you can check. The more useful question is why a market is cheap in the first place, because the same conditions that suppress the install price usually suppress the revenue behind it. This is how to judge a market from data you actually own.

Community distribution fails in a predictable way: the account gets limited, the server gets reported, or the store flags the reviews you asked for. Almost every one of those outcomes is described in a published rule you can read before you write the first message. This is what those rules actually say, and where they cannot be quoted at all.

You doubled the budget and the cost per install went up, so someone concluded the campaign is broken. It usually is not. Audience depth is finite, a tighter target narrows the pool you are allowed to buy from, and the edits people make in a panic cost more than the saturation they were meant to fix.

Somebody has sent you a slide with a push opt-in rate and an open rate on it, and asked why your app is below both. The honest answer is that the two numbers were almost certainly not measured the same way yours are. This piece explains what makes cross-app push benchmarks structurally incomparable, and what to build instead.

Every performance team has been told that raising the budget resets the algorithm. Google does not document it that way — the triggers it publishes for the Learning status are bid strategy events, and the budget cautions live in a different place with different conditions attached. This is the operational method for stepping spend up without paying for the same calibration twice.

Every Indian app team eventually asks the same question: TikTok is gone, so where does the short-video budget go? Most answers you will find name a list of domestic platforms without showing you a single line of their advertising documentation. This one is built the other way round, from the ad managers whose rules we could actually read.

AI apps can grow revenue while losing money on their heaviest users. This guide shows founders how to cost every AI action, model the usage tail, set honest limits and price for durable contribution margin.

Firebase says one install count, your MMP says another, and Play Console says a third. Your event has vanished into a row marked "(other)". Nothing is broken. Firebase is a batched, aggregated reporting system and you are reading it like a database — this is what it is actually doing, and which of the three numbers belongs in a board pack.

You uploaded the build, your colleague installed it in minutes, and the fifty external testers you promised a link to have nothing. Nothing is broken. TestFlight has a documented set of build states, internal and external distribution follow different rules, and almost every "TestFlight is stuck" complaint is one of five states with a named fix.

Revenue fell off a cliff overnight, the Policy centre says ad serving is limited, and Google will not tell you why. There are exactly three documented causes, they call for completely different responses, and one of them is not a punishment at all. Here is how to tell which one you have — and what carries on paying while it runs.

The budget is set, the campaign is enabled, and Google is spending nothing — or it was spending fine until Tuesday. These are not the same problem, and neither is the campaign that spends happily while your CPI climbs every week you scale it. Four distinct failures, each with its own diagnosis, and a triage order that stops you from changing settings that were never wrong.

Money left the account, the campaign is live, and two dashboards disagree by 35%. Somebody is going to ask which number is true, and the honest answer is that all of them are — because Meta, your MMP, Play Console and Google Ads each count a different event and call it an install. Here is what each one actually measures, how much gap is normal, and how to reconcile them in half an hour.

The chart says you lost more users than you gained, and your app is not dying. Play Console counts a device that has simply gone quiet for 30 days as a loss, and counts an acquisition far more strictly than it counts a departure. Both definitions are published. Once you read them, the crossing lines stop being alarming and start being useful.

You submitted on Monday, it is Thursday, and the status has not moved. Apple publishes no review-time commitment, so nobody can honestly tell you how long it will take — but Apple does publish every status your app can be in, and most of them are asking you for something specific. Here is what each one actually means and which ones you are supposed to act on.

Nobody puts crash rate on the growth dashboard, so nobody sees it charging rent. Google reduces the visibility of apps that cross its published thresholds, can put a warning on the store listing visitors are reading, and says outright that a larger app hurts install success. Every one of those raises what you pay for a user — and Google Ads itself tells advertisers to go and check vitals.

Sign-in works on your device, works on the tester’s device, and fails for every real user the day you go live. Nothing in your code is wrong. Google Play re-signs your app with a key you have never seen, and the fingerprint you registered with Google Cloud belongs to a different certificate entirely. Three keys are in play, and knowing which is which resolves this in ten minutes.

Your rating fell further than the new reviews should allow, and you cannot work out why. Google Play does not show users a lifetime average — it shows a figure weighted toward recent ratings, which is why a bad fortnight moves it so hard. The same mechanism is why recovery is faster than the arithmetic suggests, and there is a documented way to accelerate it.

Google will not accept new apps or updates on Billing Library 7 or below from 31 August 2026, and there is a documented extension route to 1 November if you need it. Your live app keeps working either way — what you lose is the ability to ship. Here is exactly what version 8 removed, why restore purchases is the hard part, and the order to migrate in.

Installs fell off a cliff, the app is still live, nothing was released, and nobody changed a campaign. There are seven documented causes, two of which restrict your distribution without removing your app, and one of which quietly makes you unavailable on newer devices. Here they are in the order that costs you the least time to check.

Your payback period is six months and your LTV:CAC looks healthy, so the model says spend more. The model is not wrong — it is answering a different question. Ad spend leaves your account in days, store revenue arrives up to 45 days after the month it was earned, and the platform keeps its share first. That gap, not your payback period, sets your ceiling this month.

Every article about buying installs says "you could get banned" and none of them describes what being banned is. Google publishes four distinct enforcement actions with sharply different consequences — one keeps your ratings, one destroys them permanently, and one takes every account you own. This is what each costs and what survives.

Your CRM reports 94% delivered. Your session data says almost nobody opened the app. Both are correct, because "delivered" in a push dashboard does not mean what founders think it means. This is the whole Android delivery chain, the point at which each link breaks, and how to prove where yours is failing.

Google publishes exact numbers at which Play begins hiding your app, and most founders have never seen them. This is every current threshold, what they actually measure, why your crash reporter disagrees with Play Console, and the memory and code-optimization vitals arriving in February 2027.

An AI agent can solve a hard problem today and recreate it next month, because the lesson stayed in the conversation instead of the repository. A project bible is the smallest durable knowledge system that stops that happening — eight layers, each one routed, dated and owned, with a check attached to every rule that matters.

A passing test does not prove a bug is fixed unless you know the test would fail when the defect returns. This is the nine-step method we use to close a defect with evidence: define the invariant, reproduce the failure, add a guard that fails, repair at the correct authority, then deliberately reintroduce the bug and prove the guard catches it.

A constant can look reasonable and still be wrong at a boundary. A lookup table can name the right organisation and contain a transcription error. Documentation can describe behaviour the app stopped performing two releases ago. This is the method we use to turn every real-world claim in a product into something you can re-run on demand.

Part 11 of our AI product development methodology series. A screen-by-screen review can confirm that every form, chart and report works while missing the defect that connects them. The deeper unit of audit is data — pick the three objects whose corruption would hurt most, then name every path that can create, change or destroy them.

Code review can confirm that a colour token was used. It cannot tell you whether the screen feels balanced, whether the heading wraps badly at accessibility text sizes, or whether the success message disappears before anyone reads it. This is part 10 of the AI Product Development Methodology series: the four evidence layers a real audit needs, and the rule that stops one layer closing another layer’s claim.

Give an AI coding agent a beautiful screenshot and it will reproduce the visible surface while quietly breaking everything the screenshot cannot show — normalised units, edit identity, offline retries, entitlement checks, accessibility order. This is the five-contract, nine-phase workflow we use to turn an approved design decision into a bounded patch instead of an uncontrolled reconstruction.

The quality of an AI audit depends far less on how forcefully you ask for expertise than on what evidence you require. This is the eight-part prompt contract we arrived at after repeatedly auditing a real iOS and Android product and watching broad, confident prompts declare finished areas that were not finished.

The strongest AI-assisted workflow does not ask one tool to think, design, build and verify. It splits four responsibilities — strategic synthesis, visual exploration, repository execution and independent verification — and defines what evidence each one is allowed to produce. This is part 7 of the AI Product Development Methodology series.

Design boards are useful when they make decisions visible and dangerous when they make speculation look implemented. This is the bounded, screen-by-screen board method we used on a real iOS and Android product: one surface, one question, every state that matters, a fixed evidence pack, and a runtime comparison that decides whether the board was right.

Most redesigns start with the first screen someone opens, which is how a product ends up with twelve individually improved surfaces and no centre. A UI/UX strategy is the decision system that comes first: nine layers that turn product evidence into rules a designer, a reviewer or an AI agent can be held to. This is the method, with the one-page charter and the prompt we use to produce it.

Most audit folders contain hundreds of images and almost no evidence: polished happy paths, inconsistent crops, no error states, and design concepts sitting unlabelled beside production captures. This is the method we use instead — choosing every screenshot backward from the claim it has to prove.

Before you redesign anything, you need proof of what exists — not a sitemap, not a folder of attractive screenshots. This is the seven-register inventory method we used to map a product with 51 screens and seven sheets on one platform alone, and still find unreachable capabilities, missing recovery states and data changes with no edit button anywhere in the interface.

The first instruction you give an AI agent on an existing product should be an instruction to investigate, not to improve. This is the discovery method we run before any AI-assisted audit, redesign or implementation: eight artefacts, nine steps, and an evidence label on every claim.

AI can make a product look finished in a weekend. Looking finished and being trustworthy are different states, and only one of them survives contact with users. This is the ten-stage method we settled on for using AI to investigate broadly while letting evidence — not confidence — decide what is true.

Most paywall tests never produce a decision — the sample was too small, the metric was the wrong one, or the winner shifted users onto a cheaper plan and quietly cost money. This is the test catalogue and the method: what to test in what order, how much traffic each test class actually needs, and which mistakes void the result before you read it.

Most ASO tool roundups are written by people who have never had to justify the invoice. This one is written by an agency that pays for these tools, checked every price against the vendor's own page in August 2026, and will tell you plainly when the answer is to buy nothing at all.

Most teams pay for a product analytics tool a year before they need one, and then never instrument it properly. This is a vendor-by-vendor comparison of the mobile analytics tools worth using — Firebase, Amplitude, Mixpanel and PostHog — with every free-tier allowance checked against the vendor's own pricing page as of August 2026, and a plain answer on when free is genuinely enough.

We built and shipped an iOS app almost entirely through Claude Code. Eight of the ten critical review findings sat in persistence, sync and account identity — and not one sat in the UI we were watching every day. Here is the rules file, the review loop and the audit prompt that came out of it, and the failure behind each one.

Localisation is the only ASO change that creates new demand instead of fighting harder for demand you already compete in. This is how to choose locales from your own install data, rebuild a keyword set in a language rather than translating one, and decide which assets are worth localising — including the Indian-language opportunity almost every Western ASO guide ignores.

Play Console gives you a free A/B testing engine for your store listing, and most teams misread its rules before they run a single test. This is the mechanics guide: what the console will and will not let you test, how the traffic split and the target metric actually behave, and how to read a result that comes back as a draw.

Almost no app dies of one dramatic failure. It dies of a sequence: nobody found it, the few who did left on day one, and the numbers were too small and too flattering to show either problem in time. This is the failure taxonomy we have watched play out across a decade of launches, and the parts of it you can still fix.

A soft launch is not a bigger beta. It is a paid, live, revenue-generating test of whether your app can be bought profitably — run in a market small enough that being wrong is cheap. Here is how to pick the market, size the spend, and write the go and no-go gates before you start.

The first 100 users are not a smaller version of the first 100,000. They are a different job, done by hand, with no money. This is the playbook for that stage: the free rails both stores already give you, how to use communities without getting banned, what a Product Hunt or subreddit launch honestly returns, and the three gates you should clear before you spend a rupee on installs.

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.

The Google Play Install Referrer API is the quiet workhorse behind Android attribution. It hands your app three data points — the referrer URL and two timestamps — and the gap between those timestamps is exactly what lets your MMP detect and block click injection and click spam.

Mobile ad fraud quietly drains a large share of user-acquisition budgets every year. This is a practical 2026 guide to the fraud types, the data signals that expose them, and the layered defences — MMP fraud filters, the Play Install Referrer, allowlists and post-install validation — that actually protect your spend.

ROAS, CAC, LTV:CAC and payback period are the four numbers that decide whether paid growth funds itself or quietly drains your runway. Here is how to calculate each one correctly, why the 3:1 ratio is a rule of thumb and not a law, and how to allocate a UA budget by marginal ROAS in a low-ARPU market.

Most apps are free to download, so the revenue question is not 'do we charge?' but 'how?'. This playbook compares the four monetisation models — subscriptions, one-off IAP, in-app advertising, and hybrid — by ARPU, audience fit, and the low-ARPU India reality, then shows how to sequence them as you scale.

Most IAP revenue comes from a tiny share of users, and most teams chase that revenue with generic offers shown at the wrong moment. Here are eleven tactics — starter packs, contextual triggers, spender-tier segmentation, friction cuts and India-specific microtransactions — that actually move in-app purchase revenue, with the benchmarks to aim for.

A 'good' free-trial conversion rate is meaningless without the model attached: freemium converts at 2.6%, a no-card opt-in trial at 18.2%, and a card-gated opt-out trial at 48.8%. Here are the 2026 benchmarks by model, vertical and trial length — and why card-gated trials quietly fail in India until you swap the card for UPI Autopay.

Freemium, free trial, and hard paywall are not interchangeable defaults — they are three different bets on how your app earns. Hard paywalls convert roughly 6x freemium but reach far fewer people; soft paywalls convert better yet hard paywalls return more lifetime value. Here is how to pick the model that fits your app, with 2026 benchmarks and the India card-versus-UPI lens that changes the maths.

Hybrid monetisation — running in-app ads alongside in-app purchases and subscriptions — is now the default for roughly 72% of mobile game developers. Here is how to combine ad and purchase revenue so they compound instead of cannibalising each other, with an India low-ARPU playbook built in.

Duolingo's daily active users grew from roughly 5 million in 2020 to more than 40 million in 2024 — a ~4.5x jump driven not by buying more installs but by re-engineering retention. This is a teardown of the streak, notification, leaderboard and freemium system that compounds the habit, with the transferable lessons for your own app at the end of every section.

Most apps still treat engagement as a calendar of broadcast blasts. Lifecycle marketing replaces that with orchestrated messaging across the user journey — onboard, activate, engage, retain, resurrect — delivered through the right channel at the right stage. This guide covers the stages, channel orchestration, segmentation and triggers, and why, in India, WhatsApp is the backbone the whole programme should be built around.

In-app messages reach users who are already engaged and see view rates near 75%; push reaches users who left and converts at much lower open rates. This guide settles when each channel wins, the benchmarks to plan against, how they combine across a lifecycle, and the India-specific WhatsApp and SMS reality most global playbooks ignore.

A reference table of DAU/MAU "stickiness" benchmarks by category for 2026 — messaging, social, gaming, fintech, B2B SaaS and e-commerce — plus what the ratio actually measures, where it lies to you, and the engagement metrics that have to sit beside it. The data, not the playbook.

Acquisition tells you who arrived. Product analytics tells you what they did next — and why most of them left. This is a marketer-first guide to the AARRR funnel, drop-off analysis, cohorts, the North-Star Metric and the event instrumentation that makes all of it trustworthy.

Most apps lose the majority of new users within three days, and onboarding is where that loss is decided. Here is the practical onboarding playbook — funnel diagnosis, time-to-first-value compression, the deferred sign-up decision tree, contextual permissions, and India-specific tactics — that turns first-session installs into week-one retained users.

Activation is the moment a new user first feels your app's core value — and it predicts retention better than any vanity metric. This playbook shows how to find your activation metric, shorten time-to-value, instrument it properly, and run experiments that move the number.

A funnel is a one-way pipe that leaks; a growth loop is a closed circuit where the output of one cycle becomes the input of the next. This guide explains viral loops, content and UGC loops, paid loops, the k-factor and cycle time, network effects, how to measure a loop, and why India-first apps compound fastest through WhatsApp and vernacular content.

Most apps spend heavily to acquire users and almost nothing to keep the ones quietly slipping away. This playbook covers how to define dormancy, segment lapsing users, run a 30/60/90-day re-engagement sequence, pick the right channel — push, email, in-app, and WhatsApp-first for India — and measure reactivation without spamming your way to an uninstall.

Retention is won and lost in the user experience, not the visual design. This is a practitioner's guide to the UX changes that actually move retention — reducing friction, designing habits with the Hook Model, and using gamification that engages instead of annoying.

Mobile attribution is how you connect an ad click to the install and the revenue it produced. This guide explains what an MMP does, how matching actually works, what privacy changed on iOS and Android, and how to set up attribution correctly without inventing numbers.

After ATT, iOS attribution runs on Apple's privacy-preserving APIs. SKAdNetwork 4 still works but is in maintenance mode; AdAttributionKit is where Apple is heading. Here is how each one works, where they differ, and why you should run both in 2026.

Attribution tells you which ad got the last click — not which spend actually caused the install. This is how incrementality testing and media-mix modelling measure causal lift, why they layer on top of attribution rather than replace it, and when each is worth running.

A reference table of D1, D7 and D30 retention benchmarks by industry for 2026 — social, fintech, productivity, gaming and e-commerce — plus the "7% rule" and how to read your own numbers without fooling yourself. The data, not the playbook.

Most paid ASO suites repackage data the stores already give you for free. Here are the three free first-party tools that actually move rankings — Apple Search Ads keyword popularity, Play Console experiments and the App Store Connect search-term report — plus a complete ASO stack for under $30 a month.

The App Store and Google Play convert your currency — they do not localise purchasing power. A $9.99 plan FX-converted to ₹830 prices most of India out. Here is how to set app prices country by country with purchasing-power parity, the exact store mechanics, and the India-first methodology.

Card-gated free trials structurally fail in India, where credit-card penetration is roughly 8%. This is how UPI Autopay e-mandates power recurring app subscriptions — the real ₹15,000 cap, the ₹1 lakh exception, and how to build an India subscription flow that actually converts.

Most paywall redesigns move nothing because they change the skin, not the structure. Here are the six decisions — placement, trial model, hard versus soft, and the tests worth running — that actually shift subscription conversion, with 2026 benchmarks from more than 16,000 apps.

A reference set of 2026 ARPU, ARPPU and LTV benchmarks by app category — what to expect per user, the roughly 2.7x iOS-versus-Android revenue gap, and why retention is the multiplier that decides lifetime value.

Pricing is the highest-impact experiment most app teams never run. Here is how to test in-app purchase prices and trial models without wrecking lifetime value — what the trial-conversion data shows, how to price for India, and how to design a clean test.

Google Play still drives the volume, but the Galaxy Store, Indus Appstore, Xiaomi GetApps and Huawei AppGallery each open reach and billing economics Play cannot. Here is a 2026 decision framework for which alternative app stores actually earn their place — and which to ignore.

PhonePe's Indus Appstore is the most India-native Android store yet — 100M+ devices, Tier-3 reach, vernacular and voice search, and zero commission on in-app purchases. Here is how it works, how to publish, and where it actually pays off.

The Galaxy Store is preloaded on roughly a billion active Samsung devices, and since May 2025 it pays developers 80/20 on apps and games. Here is how to submit, what drives ranking, and where it actually pays off versus Google Play.

Xiaomi's GetApps ships preinstalled on millions of MIUI devices across India — and unlike Google Play, it gives you a dedicated keyword field to index. Here is how to submit, which metadata fields actually rank, and when the effort pays off.

Huawei AppGallery reaches a large Google-less audience, but it carries a stale myth and low India relevance. We debunk the dead '100% revenue' promo, explain HMS Core publishing, map the ASO fields that rank, and say plainly where it pays off.

Apple and Google rank apps on fundamentally different signals — Apple indexes a hidden 100-character keyword field and ignores your description, while Google full-text-indexes a 4,000-character long description. Here is exactly how the two algorithms differ, with the primary-sourced data, and why one ASO playbook cannot serve both stores.

A newly launched Indian bill-payment, utility, and rent-payment app wanted volume and real transactions — fast, from a standing start in one of the most commoditised categories in India. In 8 months we drove 10M+ installs (6.84M through Google UAC alone at ₹5.77 CPI), a 4% install-to-payment conversion rate, and ₹100 crore-plus in payments processed. Here is the full-funnel Google + ASO + YouTube playbook that did it.

A new SEBI-registered stock broker app entered one of the most saturated app categories in India — dominated by four well-funded incumbents. In 90 days, we ranked it #1 for "demat", "demat account", "free demat account", and 4 more category-defining keywords on the Indian Play Store — with all 10 target keywords landing in the top 3. Here is the full 6-layer playbook — paid-impressions priming, listing experimentation, backlink campaigns, YouTube brand juice, and the affiliate-led reputation push.

Most AI coding tools are a single agent improvising. AI App Studio is a structured 17-role team — CEO, engineers, code reviewer, QA, release manager — that takes your one-line idea from scope to shipped iOS and Android app, with two human gates and everything else running autonomously. This is the full playbook on what it is, how it works, and why it changes the economics of shipping mobile apps.

Agentic Android development is not autocomplete by another name. This guide covers exactly how to install Claude Code, configure a production CLAUDE.md, choose the right skill packs, and run real Kotlin/Compose workflows — including the honest pain points every Android team hits first.

Android migration backlogs stall because mechanical converters map syntax, not idioms. This guide shows how Claude skills — for XML-to-Compose translation, state hoisting, performance, and Java-to-Kotlin modernisation — collapse a six-month migration into weeks of focused, reviewable work.

Claude can write Android code, but without the right tooling it cannot see the running app. Wiring Maestro MCP, OpenTester, and ADB MCP servers into Claude Code closes that device-visibility gap — turning the agent into a QA engineer that writes, runs, and triages tests end-to-end.

A single CLAUDE.md silently degrades beyond 15-20 Gradle modules. This guide covers the three additional axes — subagents, skills, and MCP servers — that turn Claude Code into a teammate that actually scales to a 50-engineer Android org.

Xcode 26.3 shipped the Claude Agent SDK as a first-party integration — not a plugin, not a beta. This guide covers the complete setup: built-in MCP, XcodeBuildMCP, AXe simulator control, the ios-simulator-skill, and the CLAUDE.md template that closes the visual preview loop.

Shipping is the bottleneck — not code quality. This guide walks through the complete pipeline: SwiftUI skills, App Store Connect MCPs, fastlane automation, screenshot generation, and Apple policy minefields every Claude-assisted iOS project needs to navigate in 2026.

UIKit migration sits on every iOS backlog like a tax bill nobody wants to file. With Claude Code, the right skill scaffolding, and a disciplined build-and-verify loop, individual screens now migrate in an afternoon — not two sprints. Here is the 2026 playbook that makes it tractable.

Traditional ASO tooling was replaced by a Claude skill stack in 2026. This guide covers the seven layers of automated ASO — keyword research, metadata generation, screenshot copy, localisation, competitor intel, review mining, and rejection prevention — and the five skill repos driving the shift.

The fragmentation tax that defined mobile marketing for a decade is finally getting refunded. This guide walks through every layer of the MCP-connected stack — attribution, analytics, subscriptions, engagement, and ads — with real install commands, real prompts, and honest limits every operator must know.

A skilled copywriter ships 8-12 ad variants in a week. Claude ships 50+ in four hours — and spends the rest of the week mining 5,000 reviews, localising 30 store listings, and running statistically rigorous A/B tests. This is the compound-workflow playbook.

iOS installs cost more, attribute differently, and require a different channel mix than Android. This guide covers every legitimate channel for buying iOS app installs in 2026 — with real CPIs, budget guidance, and the quality checks that separate real users from fraud.

Android installs are structurally cheaper than iOS, but only if you know which channels to use, how to protect quality, and how to time a burst that actually moves Google Play rankings. This is the complete 2026 playbook.

Apple Search Ads consistently delivers the highest-intent iOS traffic of any paid channel — yet most teams under-optimise it by treating it as a simple keyword auction. This guide covers every layer: campaign architecture, keyword strategy, Custom Product Page integration, AdAttributionKit measurement, India market opportunity, and the benchmarks we see across 300+ managed apps.

Apple doubled the Custom Product Page limit to 70 in October 2025 and opened CPPs to organic search results in July 2025. This playbook covers how to structure all 70 pages, assign keywords without cannibalisation, connect them to Apple Search Ads, and measure results with SKAN 4 — the same system our portfolio uses to achieve Apple's published 156% CVR uplift benchmark.

TikTok is no longer optional for mobile app user acquisition. This playbook covers campaign setup, creative formats, Pangle network, MMP integration, and the CPI benchmarks you should expect in 2026.

Your store listing is the last gate between a search result and an install. This guide covers every lever that moves App Store CVR — benchmarks by category, screenshot design, icon A/B testing, App Preview video lift, ratings influence, feature graphic on Google Play, Apple PPO vs. Store Listing Experiments, and seasonal updating.

Choosing the wrong MMP costs you more than the subscription fee — it costs you campaign visibility, attribution accuracy, and the ability to optimise towards real revenue. Here is how AppsFlyer, Adjust, and Singular compare in 2026 across every dimension that matters for growth teams.

Creative is now the single most decisive variable in mobile UA — accounting for approximately 56% of incremental app installs. This guide covers every format in the 2026 taxonomy (UGC, AI-generated, polished produced, motion graphic, gameplay capture, testimonial), hook science, platform-native adaptation, creative refresh cycles, and AI tooling — with specific numbers for fintech, gaming, and India Tier 2/3.

Push notifications are the highest-return retention channel in mobile — and the fastest route to an uninstall if you get the strategy wrong. This guide covers iOS soft-ask timing, Android 13 permission changes, segmentation tiers, personalisation at scale, and the 30-day onboarding sequence that consistently delivers 2–3× D30 retention across our portfolio of 300+ apps.

A practical subscription operating system for founders: choose the value boundary, test paywalls and trials, localise pricing, model store fees, recover billing failures, and read cohorts without inventing universal benchmarks.

India's fintech market is a ₹65B+ opportunity with regulatory rules that make or break every campaign. This guide covers UPI acquisition triggers, SEBI/RBI/IRDAI compliance for creatives, CPI benchmarks by sub-vertical, and the vernacular ASO edge that most growth teams leave untapped.

A well-engineered referral programme can make every new user you acquire bring in another — lowering your blended CPI, raising LTV, and compounding growth exponentially. This guide covers the K-factor formula, incentive design, WhatsApp-first sharing in India, fraud prevention, and how referrals fit alongside a paid UA stack.

Most "fast install" hacks blow up your ranking, drain your budget, or get your app suspended. These seven tactics deliver real installs in 72 hours — and they actually retain users.

Category ranking is a different game from keyword ranking. This is the playbook we use to push apps into the top 10 of their category and hold the position.

Mass UA is not about spending more — it is about building a system where every rupee multiplies. Here is the blueprint we use to scale apps past 100K installs per month.

"Buy app installs" returns a thousand sketchy vendors. Most will get your app suspended. Here are the channels that genuinely work, the red flags to spot, and how to evaluate a vendor in 10 minutes.

Most teams default to whichever channel they tried first. Here is the honest 2026 comparison across pricing, quality, attribution, and scalability — plus the stage-based framework for deciding which channel earns your next rupee of paid spend.

Indian CPI benchmarks vary 10x across categories and 3x within the same category depending on channel and tier. Here are the real numbers from our portfolio and how to bring yours down.

Gaming is the largest mobile category in India by install volume — and the most ruthless on CPI economics. Here is the playbook for hyper-casual, mid-core, and real-money apps.

Most ecommerce app marketing fails because teams optimise for installs instead of first purchase. Here is the install-to-buyer playbook that scales repeat revenue.

EdTech marketing has two buyers, multiple seasons, and a trust barrier higher than any other vertical. Here is the playbook that works for K-12, test prep, and upskilling apps.

Spending more on acquisition while retention is broken is the most expensive mistake in app growth. Here is the D1, D7, D30 retention playbook — benchmarks by vertical, onboarding optimisation, push strategy, churn prediction, and re-engagement sequences that actually compound LTV.

Healthcare app marketing is constrained by privacy, regulation, and a higher trust bar than any other consumer vertical. Here is the playbook that works.

How we took a regional Indian fitness app from 15K MAU to 213K MAU in 9 months — the channel mix, creative system, and retention loop that made the math work.

Food delivery is one of the toughest verticals to compete in — duopoly markets, supply-side cost, and a frequency game. Here is the playbook for new entrants and specialised players.

Social apps die from empty feeds, not from low installs. The playbook for niching down, seeding content, and crossing the cold-start chasm.

Spotify wins globally, but niche music and podcast apps still dominate categories like Hindi devotional, regional language, and audio-only content. Here is how.

How a small studio took a stack-runner hyper-casual game to 2M installs at ₹4 blended CPI in 8 weeks with a disciplined creative pipeline and rewarded-ad economics.

Vernacular EdTech is one of the most under-served opportunities in India. Here is how we took a Hindi-Marathi learning app from 25K installs to 412K in 6 months — and the lessons that apply to any regional language app.

Real estate is the highest-LTV install in mobile but the hardest to attribute. Here is the buyer-intent playbook for property apps and broker platforms.

Indian travel rebounded hard post-pandemic. MakeMyTrip and Goibibo dominate but niche players (homestays, religious travel, train-only) are winning meaningful slices.

Insurance app marketing is a trust game played over weeks. Compliance constraints + high CAC + long decision cycles make it one of the toughest verticals — and one of the most rewarding.

Basic ASO gets you to page one. Advanced ASO keeps you there — and pushes you to position one. This is the full 2026 playbook: semantic clustering, AI-era discovery signals, competitor keyword poaching, localisation as a multiplier, and review velocity engineering.

No one outside Google knows the exact Play Store algorithm — but five years of experiments across our portfolio give a clear-enough picture of what moves rankings.

The iOS App Store algorithm rewards different signals than Play Store. Here is what we know about iOS ranking in 2026 — based on our experiment portfolio and Apple's published documentation.

ASO A/B testing sounds simple — it is full of statistical traps that produce false winners. Here is the framework we use to test smarter and lift conversion 30%+ reliably.

Apple and Google editorial teams pick apps to feature on Today tab and Editor's Choice. Get picked once and you can see 50K-500K incremental installs. Here is how.

Our annual look at the Indian mobile marketing landscape — install trends, CPI movements, channel shifts, category dynamics, and what we expect next.

LTV-to-CAC ratio is the single most important number for app marketing decisions. Here is how to calculate it correctly, the benchmarks for your category, and what to do when the ratio breaks.

The iOS-vs-Android launch decision is rarely simple. Here is the decision framework — based on market share, monetisation, geography, development cost, and store policy.

Most launches under-perform because marketing starts at launch. The 30 days before launch are when most of the leverage actually lives. Here is the playbook.

The single most common founder question we get is "how much should I budget for marketing?" Here are honest year-1 budget benchmarks by stage and vertical for India.

Meta remains the most powerful paid channel for consumer app installs at scale. This 2026 playbook covers Advantage+ App Ads, SKAN 4 attribution, creative strategy, audience structure, and bidding mechanics—everything you need to run campaigns that compound.

Scaling from 10K to 1 million downloads is a categorically different game. This playbook covers the mindset shifts, channel stack, creative velocity, global expansion tactics, and retention mechanics that separate apps that plateau from the ones that compound to 1M.

The first 10,000 installs are the hardest—and the most important. Here is the exact launch playbook we use across our portfolio: pre-launch community building, a coordinated launch week, day-one ASO, micro-influencer cold outreach, review velocity, and your first paid experiment.

App Store Optimisation compounds because the work improves both ranking and conversion. This guide covers the ASO stack end to end and shows how to choose a partner that can actually move organic installs.

Downloads stalling? Here is the 2026 playbook we use across 300+ apps—covering ASO, paid UA, social and creator tactics, referrals, ratings, and retention loops that turn installs into compounding growth.

Not all app install services are equal. This guide explains how to evaluate providers on what actually matters — post-install quality, fraud protection, MMP integration, and vertical experience — so you hire an agency that grows your app, not just your download count.

ASO in 2026 is not a checklist—it is an ongoing growth discipline spanning keyword research, creative testing, and platform-specific tools that Apple and Google keep shipping. This guide covers every lever, treated separately for iOS and Android, with conversion benchmarks drawn from our portfolio of 300+ apps.

A real app marketing company should do more than buy installs. The right partner ties ASO, paid UA, creative testing, analytics, and retention into a single operating system that compounds growth and protects runway.

ASO in 2026 looks fundamentally different from 12 months ago. Apple Intelligence has replaced keyword stuffing with semantic relevance, CPPs have doubled to 70 pages and now influence organic search, and Google Play's Gemini-powered recommendations weight retention over raw download count. Here is what changed and exactly what to do about it.

A strong ASO company in India should improve ranking, conversion, and organic installs together. Here is how to separate real operators from generic agencies.

Google Play has its own algorithmic quirks that savvy ASO practitioners use to rank higher and convert more. This guide covers the best Android-specific ASO hacks — from AI recommendation signals and long description keyword density to Store Listing Experiments and pre-registration — that are producing measurable ranking lifts in 2026.

Most mobile marketing companies in India sell channel execution. The best ones combine ASO, paid UA, analytics, and creative into one growth system. Here is how to choose the right partner.

App promotion companies in India range from single-channel specialists to full-stack growth partners. This guide shows how to choose the right model for your app stage and avoid expensive mistakes.

Every ASO ranking factor, ranked by impact — from building a keyword universe to Custom Product Pages, off-metadata signals, and the measurement framework that separates compounding programmes from one-off tweaks. Built from first-hand results across 300+ apps.

App Store Optimisation is the highest-ROI channel for sustainable app growth. This step-by-step guide walks you through every ASO lever — from audit and keyword research to A/B testing, ratings, and measuring results — so you can rank higher and convert more visitors into installs.

A Hindi news app wanted to rank for "hindi news" and "latest news"—the most competitive keywords in their category. Here is how we did it, and drove 300,000 downloads in the process. (Anonymised client results.)

The Indian app marketing landscape has changed dramatically. Here's how to evaluate agencies that can actually move your installs, rankings, and revenue.

A regional language OTT app asked us to help them compete against Netflix and Hotstar. Here is how owning the regional keyword space and using content clips as ads drove 1M+ downloads, 51% activation, and a 65% lift in watch time.

Dating apps live or die on gender balance and geographic density. Here is how we helped a regional app reach 500K users with a 60/40 ratio, 42% D7 retention, and stronger city density in 12 months.

After the FTX collapse, trust became the core growth problem for crypto apps. This case study shows how a trust-first ASO, review, and referral system took an Indian exchange from 45K to 250K users.

A leading Indian trading app needed quality installs, not just volume. Here is how we drove 180,000 installs at ₹8 CPI with strong retention using trust-first ASO and value-based UA.