Software development
Mobile app development, starting with whether you need one
Most businesses that want an app need a good mobile website. The ones that genuinely need an app need it for a specific reason, and that reason shapes everything.
Context
When an app is the right answer
An app earns its place when you need something the browser cannot do well: working offline in a truck or a basement, push notifications people actually act on, camera and barcode workflows, background location for a field team, or an interface used every day by staff who need it to be fast.
If the need is "customers should be able to book from their phone", that is a mobile website, it costs a fraction as much, and nobody has to install anything. We will say that before quoting an app.
When an app is right, the platform decision follows the requirement. Cross-platform covers most business applications from one codebase. Native is worth the extra cost where hardware, performance, or platform-specific features are central.
Scope
What is included
- The honest conversation about whether an app is the right shape
- Cross-platform or native, chosen from the requirement rather than habit
- Offline behaviour and sync design where field use demands it
- App Store and Google Play submission, including the review process
- Release management and update pipeline set up for your team
- Store accounts in your name, always
FAQ
Questions people ask
Native or cross-platform?
Cross-platform for most business applications — one codebase, both platforms, materially less to maintain. Native where hardware access, heavy graphics, or platform-specific behaviour is central to what the app does. The requirement decides it, not our preference.
Do you handle App Store submission?
Yes, including the review process and the rejections that come with it. Store accounts are registered in your name, so you keep control of your own listings and can move to another developer without an argument.
What does maintenance involve?
Both platforms release annually, deprecate APIs, and periodically change store requirements. An app left alone for two years usually needs meaningful work before it can ship an update at all, which is why we price maintenance in rather than treating it as optional.
Related
Next step
Find out what this would look like for you
A 20-minute call. We ask what breaks, what it costs you, and who handles it now. If we are not the right fit we will say so.