There's a tendency in software to add features. Something starts as a simple idea and then grows: more settings, more screens, more integrations, more options. The original purpose gets buried under layers of functionality that was added because someone thought it might be useful, or because a competitor had it, or because it seemed like the sort of thing an app in this category should do.
By the time it ships, the app is trying to do ten things and doing none of them particularly well.
We try to go the other way. Every app we make at Victain does one thing. The meal planner plans meals. The water tracker tracks water. The calculator calculates. That's it.
It makes the design clearer
When an app does one thing, there's no navigation puzzle to solve. There's no settings menu you need to explore before you can use it. There's no onboarding flow explaining features you haven't asked for yet. You open it, it does the thing, you close it.
That clarity isn't just a user experience benefit — it makes design decisions easier too. Every question about what to build or how to build it has a clear answer: does this serve the one thing the app does? If yes, consider it. If no, don't add it.
A focused brief is a gift when you're designing something.
It's faster to build and easier to maintain
A small, focused app has less code than a large, sprawling one. Less code means fewer bugs. Fewer bugs mean less time fixing things that were working fine before something else changed. It also means that when you do need to change something — update a dependency, adjust a behaviour, fix a real bug — you understand the whole app well enough to do it quickly.
Large apps accumulate complexity that nobody fully understands anymore. Small apps stay comprehensible.
It ships
Apps that try to do everything are very hard to finish. There's always one more feature to add before it's ready, one more edge case to handle, one more screen that needs building. The scope expands to fill the time available, and sometimes beyond.
An app with a tight scope can actually be done. You can reach a state where it does what you set out to build and does it well. Shipping something real that solves a real problem is better than spending another six months on a larger thing that never quite reaches the same point.
It respects the user
There's something respectful about a focused app. It doesn't try to colonise more of your time and attention than it needs. You use it for its purpose, and then it's out of the way. It doesn't send you notifications about features you haven't enabled. It doesn't show you content from other users. It doesn't have a discover tab.
People's phones are full of apps competing for attention. An app that does its job and leaves you alone is increasingly rare, and increasingly appreciated.
The features we've cut
We've made a lot of cuts over the course of building our apps. Features that seemed obvious at the planning stage that turned out to be scope creep in disguise. Community features. Social integration. Cross-device sync for apps where it wasn't needed. Analytics dashboards. Habit streaks that went beyond what they needed to be.
Almost every cut made the app better. That's not always obvious when you're making it — cutting a feature feels like giving something up. But the alternative is an app that's harder to use, harder to build, and harder to ship.
The best feature is often the one you don't add.