App Development.
Mobile and web apps that people actually open twice. Built around a real job to be done, shipped to the stores, and maintained after launch.
What this covers
Customer-facing apps
Apps your customers use to book, buy, track or get help, with the same account and data as the rest of your business. Native where it matters, cross-platform where it does not.
Internal and field apps
Tools for the people doing the work away from a desk: inspections, intake, job sheets and approvals that keep working when the signal does not.
Progressive web apps
When an install is friction rather than value, a web app that works offline, sends notifications and needs no store review.
App modernisation
An existing app that is slow, unsupported or failing review. We take it over, stabilise it, and get releases moving again.
Store release and support
Submission, review, phased rollout and the crash and usage reporting that tells you what to fix first.
How we work
We agree the one job the app has to do before anyone designs a screen. Everything else is a later release.
A clickable build in your hands early, so the arguments happen over something real rather than a document.
Two-week releases to a test device or TestFlight. You see progress continuously, not at the end.
Store submission, then crash, performance and drop-off reporting from day one, so the first fixes are the right ones.
The stack
Chosen per project, not by habit. Cross-platform unless the app needs something only native can give it.
The same team, on a platform people use all day.
We have not published a mobile app case study yet. The closest work is Transaction Hub, a platform transaction coordinators live in daily: four disconnected tools replaced by one system with an AI contract auditor. The discipline is the same, whether the screen is a phone or a browser.
Questions we get
iOS, Android, or both?
Usually both, from one codebase, unless your app needs something only a native build gives it. We tell you which case you are in before the quote, not after.
Do you publish to the App Store and Google Play?
Yes. We handle submission and review under your developer accounts, so the listings stay yours.
Who owns the code and the accounts?
You do. Repositories, developer accounts, infrastructure and documentation are in your name from day one.
What happens after launch?
Apps need maintaining: OS releases, store policy changes, and the bugs only real users find. We offer a support arrangement, and you are free to take it in-house instead.
Do you sign NDAs and handle regulated data?
Yes to both. We sign an NDA before the first call if you need one, and we build with HIPAA-aware practices for healthcare and other regulated data. We have not been SOC 2 audited, and we will say so rather than imply otherwise.