The case against all-in-one apps

There is a moment in every app's life when someone suggests the adjacent feature. The bedtime story app could also play lullabies. And track sleep. And have a forum for parents. Each one sounds reasonable. Together they turn a product into a bundle, and bundles are what people leave.

One sentence

An app that does one thing can be described in a sentence, and that sentence is the subtitle, the first screenshot, the ad and the thing a friend says when they recommend it. Every adjacent feature makes the sentence longer, and a longer sentence is found less, understood less and trusted less.

The moment test

Most adjacent features belong to a different moment in the day. Sleep tracking happens in the morning; bedtime stories happen at night. Different moment, different mood, different reason to open the app. Putting both in one app means neither is the obvious thing to tap. That is usually a sign the feature is a different product.

What it costs us

Revenue we could have had from people who wanted the bundle. Some reviews asking for the adjacent thing. Occasionally a competitor who ships everything and wins a chart for a month. We accept these, because the alternative is an app whose store page needs a paragraph.

The one condition

We add when the new thing serves the same moment, for the same person, and makes the one sentence truer rather than longer. Own-voice narration in Dreamify passed: same bedtime, same parent, and the sentence "stories told in your voice" got better. A sleep tracker would have failed every part of that test.

Several small apps, not one large one

When an adjacent idea is good, it becomes its own app with its own sentence, sharing the backbone underneath. That is how a studio ends up with three focused products instead of one sprawling one. It is slower in the short term and much easier to keep good.