"We should have an app" often comes from competitors rather than a strong need. The wrong choice wastes budget and time.
Three options
- Native mobile app (iOS/Android): Downloaded from app stores; full access to camera, notifications and sensors.
- Web app: Runs in the browser; no install and one codebase for every device.
- PWA (progressive web app): An advanced web app that can be added to the home screen, work offline and send notifications.
Comparison
- Cost: Web/PWA is usually lowest; native for two platforms is highest.
- Build time: Web/PWA goes live faster.
- Updates: Instant on the web; store apps need review.
- Hardware access: Widest in native; PWA is limited but often enough.
- Discoverability: Websites are found in search engines; apps in the store. For search visibility see the SEO guide.
Which one when?
- Web app / PWA: Admin panels, booking and order forms, internal tools, content-led services.
- Native app: Heavy hardware use (advanced camera, Bluetooth), performance-hungry graphics, frequently used loyalty apps.
- Hybrid path: Validate with web/PWA first and move to native if usage grows.
The deciding question
"Will users open this many times a day or only occasionally?" For occasional use, sending people to a store adds friction. A fast, mobile-friendly site is often enough; see how to speed up your website.
Cost and budget
Starting small and expanding as needs appear is the safest route. For numbers, see the website cost guide and planning a software budget. If you need to connect existing systems, API integration is part of the scope.
ujans designs and builds web apps, PWAs and mobile solutions to fit your need.