Mobile App Development
Honestly? Most businesses don't need one
That might sound like an odd thing to say on a mobile app page. But it's consistent with how we work — we'd rather give you the right answer than the expensive one.
When most people say they want a mobile app, what they actually want is something that works well on a phone, is easy for their customers or staff to use, and doesn't require a laptop to access. That's a completely reasonable requirement. It's just that a native mobile app — the kind you download from the App Store or Google Play — is rarely the most practical way to achieve it.
A progressive web app is usually the better choice
A progressive web app (PWA) is essentially a web application that's been built to work and feel like a native app on a mobile device. It runs in the browser, installs on the home screen, works across iOS and Android without separate development, and can support features like push notifications and camera access.
For most business use cases — customer portals, staff tools, booking systems, field reporting — a PWA delivers everything a native app would, at significantly lower cost and without the overhead of app store submissions, separate iOS and Android codebases, and the ongoing maintenance that comes with them.
If you're considering a mobile app, a PWA is almost always where we'd start the conversation.
Why native apps are more painful than people expect
For a start, you're not building one app — you're building two. iOS and Android are entirely separate platforms, which means separate development, separate testing, and separate maintenance indefinitely. On top of that, both Apple and Google charge annual developer fees, and every release — including updates — goes through an app store review process that can be slow, unpredictable, and occasionally results in rejection. Apple in particular is notorious for the hoops involved.
For most business use cases, that's a lot of overhead when a PWA would do the job just as well.
When a native app genuinely makes sense
There are situations where a native app is the right answer, and we'll tell you honestly when you're in one of them. The clearest cases are where the app needs to work reliably without an internet connection, or where it needs deep integration with the device's hardware in ways a browser can't fully support.
A good example is a mobile app we're currently building for a pest control company. Their technicians work on customer sites — often at rural properties, and other locations with little or no mobile signal. The app needs to work fully offline, synchronising data when a connection becomes available. It also needs reliable access to the device camera for documenting treatments, and GPS for accurately logging job locations. In this case, a native Android app is clearly the right tool — a PWA would let the technicians down at exactly the moments they need it most.
That's the kind of situation where native development is worth the investment. If your use case looks like that, we can build it.
Not sure which applies to you?
If you're trying to work out whether you need a native app, a PWA, or something else entirely, that's exactly the kind of question a discovery call is useful for.
