The case against subscriptions for small, focused apps

A pickleball scoreboard should not have a monthly fee. Neither should a card maker, a rep counter, or a habit tally. The moment a small, focused utility starts charging every month, it stops being judged on whether it does its job and starts being judged on whether people keep paying, and those are not the same product.

A recurring fee changes what gets built

A monthly fee needs continuous justification, and that pressure lands on the roadmap. The app has to keep looking like it is worth the charge, so features get added past the point of usefulness. A scoreboard grows a social feed. A camera tool grows a profile page. The thing that was good because it did one job well gets bulkier every quarter.

It also changes the opening screen. Subscription apps need you to come back on a schedule, so they acquire streak pressure, badges, and notifications with an interest in your attention rather than your outcome. None of that exists because it helps you. It exists because a churn number is on someone's dashboard.

Then there is the server. Charging monthly nudges you toward features with a recurring cost behind them, which means sync, accounts, and a backend — and the moment your data lives on someone's server, the privacy story becomes a policy instead of a fact.

A subscription quietly makes retention the product, and for a tool you should only open when you actually need it, that is exactly the wrong thing to optimize.

What going without one rules out

This is a real tradeoff, not a free lunch, so it is worth stating what it costs. No monthly revenue means no expensive per-user server bill, which means no feature whose cost grows every time someone opens the app. It rules out large-scale sync infrastructure and it rules out anything that must call a costly service on every tap.

That is a constraint, and constraints have to be respected honestly. Some things genuinely need a connection — live market data, a video visit with a real person — and those apps are built and described differently.

What it makes possible

Once retention is not the goal, the app can be good in the specific way a tool is good: it opens fast, does the thing, and gets out of the way. Kitchen can be two enormous buttons and a serve indicator, and it never needs to become more than that to keep earning its place.

Work moves onto the device, because on-device features have no cost curve that scales with usage. That is why so many of our apps run offline with no account: it is the architecture that a no-subscription model actually rewards.

And you can stop using an app without a decision attached. There is no cancellation to remember and no charge arriving for a tool you last opened in March. Everything we make is free with no subscriptions, ever.

The economics of small software keep improving in this direction. On-device models keep getting more capable, which keeps shrinking the set of features that need a server, which keeps shrinking the case for charging monthly for a focused tool. We expect that gap to keep widening, and the full app list is where it shows up first.