Mobile Development
Native iOS and Android, or cross-platform where that is the right call, taken through review and into both stores. For products that need the camera, notifications, offline use, or a place on the home screen.
Who this is for
- A web product whose users keep asking for an app.
- A field or operations team that needs to work offline and sync later.
- A consumer product where push notifications and camera access are core, not extras.
- An existing app that has fallen behind on OS releases and store requirements.
What is included. Tick what you need.
Artefacts, not adjectives. Each is something you can point to at the end. Tick the ones your project needs and send the list with your enquiry; we reply with a written scope.
Technologies we use for this
The relevant slice of our technology matrix. Nothing here that we cannot staff today.
- Python (Django, FastAPI, Flask)
- Node.js (Express, NestJS)
- PHP (Laravel)
- Go
- REST
- GraphQL
- gRPC
- WebSockets
- Celery
- Redis Queue
How we deliver it
The five steps every engagement goes through, in the form they take for this service.
Scope
A call with an engineer, then a written scope: what is in, what is out, and what it costs.
Architecture
Data model, API contract, and infrastructure plan, approved before code is written.
Build
Builds to your phone every week through TestFlight and internal testing, with a demo of what changed.
Harden
Tests on the paths that matter, error tracking, a performance pass, and a security review.
Launch and hand over
Production deployment, monitoring, documentation, and every repository transferred to you.
Questions we get asked
Native or cross-platform, which do I need?
Cross-platform is right for most business apps and gets one codebase into both stores. Native is right when the app leans hard on the camera, sensors, performance, or platform-specific design. We recommend one in the scope and explain why.
Do you handle store submission?
Yes, including the listings, screenshots, privacy declarations, and review feedback. The developer accounts are created in your name.
What about updates after launch?
The first 30 days of fixes are covered. After that, a maintenance retainer or a dedicated engineer keeps the app current with OS releases, or your team takes over the documented pipeline.
Can you add an app to a product that already has an API?
Yes. We audit the API for what a mobile client needs, such as pagination, auth token handling, and offline-safe endpoints, and add only what is missing.
How long does an app take to reach the stores?
Three to six months for a first release, including review. Store review itself usually takes days, and we build in time for one round of feedback.
Tell us what you are building.
We reply within one business day with how we would build it, what it would cost, and which engagement model fits.
- 01Tell us what you are building
A short form or an email. No deck required, and "not sure yet" is a fine answer.
- 02A call with an engineer
Within one business day. Technical questions get technical answers, from the person who would build it.
- 03A written scope and quote
Fixed price where the scope is defined. The document is yours whether or not you go ahead.