Insight

Sometimes businesses ask themselves: do I build a proper app, or keep everything on a mobile-friendly website? The answer is usually the website, but there are a handful of situations where an app is genuinely the right call. There is also a third option worth knowing from the start: a progressive web app, or PWA, which installs straight from the browser without going through an app store and sits somewhere between the two.

• How often will someone actually use it? If this is something people touch once or twice a year, like checking your hours or filling out a contact form, a website wins. If it is something people would open daily, an app starts to make sense.
• Does it need to work without a reliable connection? Apps, including PWAs, can cache data and function offline. A standard website generally cannot. This matters most for people working in the field: tradespeople, warehouse staff, delivery drivers.
• Does it need access to hardware a browser cannot reach? A PWA can use a camera and GPS reasonably well today. What it still cannot do, at least on iPhone, is reach Bluetooth peripherals, NFC, or USB accessories, and it has only limited access to sensors beyond the basics. If the product genuinely depends on that kind of hardware, a website cannot do it properly, and a PWA will not close that gap either.
• Does the experience itself need to feel top-tier? This is where native still wins. A native app is built with the platform's own UI library, UIKit or SwiftUI on iOS, Jetpack Compose on Android, so every component, gesture, and animation matches exactly how the rest of the phone behaves, and it runs compiled directly on the device rather than inside a browser engine. A website or PWA can get close, but if the experience itself needs to feel genuinely polished and platform-native, that is still native's advantage.
• Do you need push notifications to bring people back? PWAs have been able to send push notifications on iPhone since iOS 16.4, so the capability itself is not the gap anymore. The gap is reach: someone first has to manually add the site to their home screen before they can even be asked to allow notifications, and once you account for that whole process, the realistic reachable audience for web push ends up far smaller than native, in the order of 10 to 15 times smaller by some estimates.
• How will people actually find it? Websites get found through search. Apps get found through app stores, or because someone was told to go and download it. A website delivers value the moment someone clicks a link. An app requires someone to decide to install something before they get anything at all, which is a much higher barrier.
• Would someone actually want this on their home screen? People are genuinely reluctant to install an app for something minor. If you cannot clearly answer why someone would want your icon sitting on their phone, that is usually a sign you do not need one.

A PWA is worth strongly considering before you commit to a full native build. It covers an install-to-home-screen icon, offline caching, and now push notifications on most devices, without the cost or complexity of maintaining a native app. What is left of the gap is deeper hardware access, top-tier UX polish, and how many people you can actually reach with notifications, not the basic feature set anymore. If you are weighing this up for your own business, that is exactly the kind of decision worth talking through before you commit to a build, through a short consulting conversation.

Still have questions? Give us a call, book a quick meeting, or send us a message to understand more without any pushy sales tactics.