A cross-platform app launch: 10,000 downloads in the first month

The publisher had a validated idea, a launch date they had already told people about, and a budget that would not stretch to two native teams. Building for iOS first and Android "later" was on the table, and it would have halved the audience on day one for a product whose whole value depends on other people being on it.

So the constraint was set before the first line of code: one team, one codebase, both stores on the same day, and a build good enough that the first reviews would not sink it.

React Native was the right answer here for a specific reason rather than a general one. The app is content and forms rather than heavy graphics or platform-specific hardware work, so a shared codebase costs almost nothing in feel and saves most of the budget.

We designed to the platform conventions rather than to a lowest common denominator: navigation, typography, and the share and back behaviours follow what each operating system's users already expect, even though the code behind them is shared. Anything genuinely platform-specific, notifications, in-app purchase, deep links, sat behind a thin native layer so the rest stayed common.

Store readiness was part of the build, not an afterthought in release week. Listing copy, screenshots and the first-run experience were written and tested together, because the download is decided on the store page and the rating is decided in the first two minutes of use. Analytics and crash reporting shipped in the first build, so launch week could be steered by evidence rather than by nerves.

In the first month after release:

• more than 10,000 downloads
• a 4.8 out of 5 store rating
• 65% retention

The rating is the number we watch hardest on a launch, because it compounds: it decides how much of the following month's discovery is free. Retention at 65% told the publisher the product was worth investing in further, which was the real question the launch had to answer.