The Return of the Single-Purpose App
The Quiet Return of Small Apps
For a decade, every successful app wanted to become every other successful app. That era is ending — not with a crash, but with users quietly choosing the tool that does one thing, and does it on purpose.
For most of the last decade, the governing theory of consumer software was that every successful app should eventually become every other successful app. The messaging app should sell you things. The shopping app should let you chat. The ride-hailing app should deliver food, and also groceries, and also short videos. The platform that started as a way to book a taxi would, given enough time and venture funding, become the place where you paid your rent, applied for a loan, watched the news, and ordered a pizza.
This was not seen as mission creep. It was seen as strategy. The industry had a word for it — the super-app — and for a long time it looked like the whole world would be organized into four or five of these things.
That era is, I think, ending. Not because super-apps failed — some of them are thriving — but because the people using them have started to quietly rediscover the virtues of software that does one thing.
Part One The drift toward single-purpose
Look at what has actually been growing, under the radar, over the last two years. A wave of small, opinionated apps has been gaining ground. A dedicated reading app with no feed, no notifications, no recommendations — just your saved articles. A podcast client that refuses to become a social network. A calendar that shows your week and nothing else. A text editor that loads a file, saves a file, and does not have a marketplace of plugins for the things it does not want to do.
These tools are often expensive by the standards of modern software — twenty dollars, forty dollars, sometimes a yearly subscription — and they are doing fine.
Done well
Inside the app
Team
Meanwhile, the super-apps are still growing in users but quietly losing something harder to measure: affection. When someone tells you they love a piece of software in 2026, it is almost never the app with nine tabs of functionality. It is almost always the small, sharp one with exactly the feature they need.
Part Two Why the bundling broke
The theory of bundling was that users would pay in attention for the convenience of having everything in one place. Why open a second app when the first app can do it? Why context-switch when the same interface handles messaging, payments, shopping, and scheduling?
What the theory didn't account for was that the interface itself was becoming the context switch. Opening the messaging tab in the shopping app is not, neurologically speaking, very different from opening a separate messaging app. Your brain still has to load the mental model of the new task.
Meanwhile, the home screen of the super-app has become a kind of town square full of attention-grabbing vendors, each one trying to pull you into the feature that pays the best per click. The cognitive cost of "one app that does everything" turned out to be almost identical to the cognitive cost of many apps — except that in the super-app, you were also being continuously cross-sold.
There's also a subtler problem. A super-app can never be the best app for any one task, because every feature is competing with every other feature for space, engineering attention, and the user's working memory. The reading feature inside the messaging app will always be worse than the dedicated reading app. The payments feature inside the social app will always be worse than the dedicated payments app. And once you've used the dedicated version, the bundled version feels not just worse but almost insulting — a cheap imitation tucked inside a menu, hoping you don't notice.
The default setting of venture-backed software is to say yes. The default setting of indie software is to say no. When you use software built by someone who has to live with their own decisions, it shows.
Part Three What the small apps get right
The new single-purpose apps have a specific shape. They tend to be built by one person, or a small team. They have a point of view — a strong opinion about what the tool should and shouldn't do. They charge money, usually one-time or subscription, and they don't have ads. They do not try to be "the home for" anything. They do not have an AI assistant unless that is the whole app. They refuse features on purpose.
This last one is the real innovation, if it can be called an innovation — it is really just a return of an old discipline. For years, good software was software that said no to most requests, because every feature you add is a feature you have to maintain, explain, and defend against breaking the rest. The default setting of venture-backed software is to say yes, because every feature is an expansion opportunity. The default setting of indie software is to say no, because every feature is a burden that has to be carried by one person.
Part Four The quiet protest
There's a cultural current underneath this that's worth naming. A lot of people are tired. Tired of being upsold inside apps they already paid for. Tired of opening a tool to do one thing and being pulled into the tool's attempt to become their life. Tired of the feeling that every piece of software is, beneath the surface, trying to get them to do more inside of it — to stay longer, to explore more features, to be more engaged.
The engagement metric, which nobody outside of software companies has ever wanted to optimize, has been quietly grating on users for a long time.
The return of the single-purpose app is, in a way, a protest vote. It is users choosing the software that doesn't have a growth team. They are paying real money for software that does not want to grow inside them. They are choosing, against their own convenience, against the logic of having everything in one place, the discipline of a tool that knows its job.
Part Five What happens next
I don't think super-apps are going away. The infrastructure they provide — identity, payments, reliable delivery — is genuinely useful, and there are places in the world where they remain the primary interface to the internet for most of the population. They will continue to be important.
But I think their relationship to users will shift. The super-app becomes, increasingly, a utility. You use it when you have to. You don't love it. You don't recommend it. You don't feel a connection to it, any more than you feel a connection to your electric company.
The big story of the next few years in consumer software is the slow, unannounced return of taste — the idea that software can be a thing someone made, rather than a platform someone runs.
The apps you love, and recommend, and feel a connection to — those are going to be small again. They will be built by small teams. They will cost actual money. They will do one thing. And the cumulative effect of this on the software industry will be larger than it looks, because the apps you love are the apps you talk about, and the apps you talk about are the apps that shape what people expect software to be.
The best apps have always been the ones where you could feel the author on the other side of the screen. We went through a long period where the author was a corporation, and the thing on the other side of the screen was a product of committee and metrics. A lot of us didn't realize how much we missed the author until we started paying for them again.
Comments
Post a Comment