The indie app playbook for 2026: ship one ritual, not a platform

People ask what we would do if we were starting from zero today with one iOS app and a small team. Here is the playbook we actually follow, written as advice.

1. Pick a moment, not a market

Do not start with "the wellness market" or "the kids category". Start with a moment people repeat every day: the commute, the gym bag, the bedtime, the first coffee. One moment gives you a user, a time of day, a mood and a reason to return, all for free. A market gives you a spreadsheet.

2. Make the first output personal

Whatever your app produces, make the first one about the user. Their name, their city, their child, their stamps. This costs you a longer onboarding and some data responsibility. It buys you the single strongest retention lever there is. Generic output is easy to leave.

3. Build the engine, not the furniture

Settings screens, profile pages and share sheets can wait. The thing that makes the app worth opening cannot. Spend the first weeks entirely on the core loop and ship with the minimum furniture around it. You will learn more from one hundred real users than from a month of polish.

4. Ship in weeks, judge in week two

First version on the App Store in weeks, not quarters. Then ignore downloads and watch one number: how many people come back in the second week. If that number is bad, no amount of marketing will fix it, and you need to know before you spend.

5. The store page is the product's first screen

Before you buy a single install, make the store page earn one. First screenshot as a billboard, subtitle built from real search terms, a title that says what the app does. Paid traffic multiplies whatever the page already does, including nothing.

6. Buy attention only after the page converts

Apple Search Ads is the cleanest first channel for an iOS app, because the person searching already wants an app. Start small, in your own account, with brand and category terms separated, and raise budget only on numbers you have measured after the install.

7. Reuse your own plumbing

If the first app works, the second one should start further ahead: the same subscription setup, the same analytics, the same narration or generation layer. We shipped three apps in three months because the second and third reused the first's backbone. Different products, shared plumbing.

8. Keep one person who knows the whole app

The design, the code, the store listing, the reviews. When one person holds all of it, decisions take minutes and the product stays coherent. Add people when the moments multiply, not before.

None of this is clever. It is just the order of operations that we have seen work, and the one we use for our own apps.