service
Mobile application development
A business where the phone is genuinely the right device: field staff capturing work on site, or customers needing something in the moment.
What you get
- An honest assessment of whether the phone is the right platform, before any build.
- A working app for the core task, with the offline and poor-connection behaviour designed rather than assumed.
- A clear position on platform scope: one platform first, or both, and why.
- Release and update process, including how store review affects your timelines.
How this differs from web application development
Mobile carries distribution through app stores, device capability and offline behaviour. Those constraints change both the build and the release process, not just the screen size.
How we approach it
- We decide early whether this must be a published app or whether a well-built web interface would do the same job without an app store.
- Offline behaviour and sync conflicts are designed up front, because they are the requirement most often discovered after launch.
- Store review requirements are checked before build, since a rejected release can delay a launch by weeks.
What is out of scope
- An app that exists because a competitor has one. A responsive site is often the better commercial answer and we will say so.
- Guaranteed app store approval.
How it is priced
Cost is driven by the number of platforms supported and whether the app must work offline; offline sync is usually the largest single line.
See the pricing page for how that works in practice.
How to start
The first conversation is free and usually takes half an hour. Bring the problem as you experience it — what is not working and what you have already tried.
Tell us what you need
The more specific you are about the problem, the more useful the first reply will be. We read every enquiry ourselves.