Most people do not have one problem at a time. A single week can hold a job search, a household that needs organising, a relative who needs a hand, a bill that needs attention, and a child who still wants a story before bed. Each of those usually means a different website, a different account, and a different place to start from scratch.
That starting cost is easy to underestimate when building. Teams measure how fast a page loads and how short a signup form is, then forget the step before both of those: remembering where the tool lives at all. A useful service that nobody can find on a tired Tuesday evening might as well not exist that evening.
The hub pattern is one answer to that discovery problem. One front door, and behind it a set of standalone sites, each handling one part of life properly instead of lightly.
What worked
One address to remember. The entry point stays the same even when the problem changes. Someone arrives with whatever the day produced, follows the signpost that matches, and lands inside a full website built for that job, not a shallow feature tucked inside a larger app.
Destinations that stand on their own. The hub only works because the rooms behind it are real. Each destination keeps its own purpose, its own community, and its own data. Getting back to work, asking for and offering help, family routines, meeting people, pricing attention, classic style, steerable bedtime stories, daily guidance, and live policy debate argued in the open are different jobs, and the design treats them that way.
Letting the other rooms wait. A front door also removes a decision. Nothing needs to be browsed, compared, or triaged on arrival. The part of life that needs attention today gets attention, and the rest stays one click away without demanding any.
A thin layer that stays thin. The hub earns its place by doing one thing well: routing. It answers the question "where do I start" and then gets out of the way. Every feature added to the hub itself was a feature that made a destination harder to reach, so restraint turned out to be the main design skill.
What broke
The temptation to merge everything. Once a shared entrance exists, the next suggestion is always a shared account, a shared feed, and eventually one big app. Each step trades the clarity of single purpose sites for convenience that mostly helps the builder. The version that held up was the boring one: shared discovery, separate destinations.
Navigation naming is harder than navigation code. Labels that seem obvious in a planning doc mean little to a tired visitor. Category names had to describe the problem someone arrives with, in their words, rather than the internal name of the product behind the door. Several rounds of renaming taught more than any analytics view did.
A front door can become a bottleneck. If the hub page is slow, cluttered, or out of date, every destination suffers from a problem it did not cause. Keeping the entrance fast, short, and current is maintenance that never finishes, and it has to be treated as infrastructure rather than marketing.
The practical habit that came out of all this is simple. Start at the hub, go straight to the part of life that needs work today, and let everything else wait. A front door does not solve the week. It just stops the week from starting with a search.
That hub is onelifevibe.com, built as one entrance to a growing family of single purpose websites.
How do other builders handle rediscovery for tools people only need occasionally? Is a hub page enough, or does the starting point have to live somewhere else entirely, like a bookmark bar, a home screen, or a saved message to oneself?
Top comments (0)