Building a mobile app is one of the easiest ways for a company to spend a serious budget on something nobody opens twice. It is also, for the right business, one of the highest-leverage products it will ever own.
The difference is not technical. It is whether a repeated moment of use exists.
The test
Describe, concretely, the moment someone opens your app. Not the category of user — the moment. Where are they, what just happened, and what are they trying to do in the next thirty seconds?
If you can describe that moment and it recurs — daily, weekly, on every shift, at every delivery — an app is probably worth building. If the honest answer is "when they want to find out about us", you want a fast mobile website, and you want to spend the app budget somewhere else.
Apps that earn their place
A few patterns come up repeatedly. Products with a genuine habit loop: booking, tracking, logging, messaging, anything a customer does routinely. Products that need the device itself: camera, location, offline capability, background notifications, biometric access.
And — frequently overlooked — internal applications. Teams who do not work at a desk are often the strongest case of all. Field engineers, drivers, warehouse and in-store staff, inspectors. The moment of use is obvious, it repeats constantly, and the alternative is usually paper and a phone call.
What kills apps that should have worked
Duplicating the website is the most common. If the app does what the site does, with a worse update cycle and an install barrier in front of it, it will lose.
Adding the commercial model late is the second. Subscriptions, trials and entitlements shape the product; bolting them on afterwards means pricing and experience end up fighting each other.
And treating notifications as a growth lever rather than a service is the third. Every notification that is not useful to the user is a small withdrawal from the reason they keep it installed.
Native or cross-platform is the last question, not the first
It is the question everyone opens with, and it barely matters until the others are settled. React Native is an excellent fit when the product is mostly shared logic and delivery speed matters. Native wins when the experience depends on platform capability — heavy graphics, deep hardware access, or a specific feel that users will notice.
Decide it from the requirements, in the open, and write down why. That note will be worth a great deal in a year.
