Mobile app development
iOS and Android apps, from first sketch to store listing.
- iOS and Android
- Offline and sync
- Push notifications
- Store submission
What this is for
Software that belongs on a phone rather than at a desk. An app earns its place when it needs something a browser cannot reliably give it — the camera, location in the background, notifications, or working with no signal at all. Where none of those apply, a mobile site does the same job without asking anybody to install anything. Where an app is the right answer, it is built for both platforms and taken through the store review that sits between the finished build and its first user.
What it covers
- iOS and Android
Both platforms from one codebase where that suits the app, with the parts that genuinely differ handled per platform rather than averaged into something that fits neither.
- Offline and sync
The app keeps working with no signal and reconciles when it returns. What happens when two devices changed the same record is decided deliberately, rather than by whichever synced last.
- Push notifications
Wired up on both platforms, including asking permission at a point where the person can tell what they are agreeing to.
- Store submission
Listings, screenshots, privacy declarations and the review itself. Rejections are a normal part of that process and are handled as part of the work.
What you end up with
- Builds for iOS and Android
Signed, installable builds you can put on a device and use before either store has seen them.
- Both store listings submitted
Prepared and taken through review under developer accounts held in your own name.
- Push notifications wired up
Working end to end on both platforms, with a way for your own team to send them.
- An update path that has been tested
Shipping a second version is proven before the first is published, including what happens to data already sitting on a device.
What we need from you
- Developer accounts in your name
Both stores require an account tied to the business. An app published under somebody else’s account is difficult to move afterwards.
- Somebody willing to test on their own phone
One person on your side with the app installed and in daily use finds more than a written test plan does.
- What the app does with no signal
Whether it should keep working, queue what it cannot send, or simply say it is offline. That single answer shapes a large part of the build.
Who works on it
Each part is done by the specialist for it, in the order the work reaches them.
How it runs
- DiscoveryFirst
We work out what you need, what it has to do, and what it will cost.
- Scope written down
- Fixed quote
- Agreed timeline
- DesignBefore the build
You see the site before it is built, on desktop and phone, and approve it before the build starts.
- Designs to approve
- Mobile and desktop
- Final copy
- BuildThe build
The design is built to its measurements, on a link you can open at any point during the build.
- Live preview link
- Progress you can see
- Content loaded
- LaunchHandover
Domain, hosting and email pointed at the new site. Checked on real devices, handed over in your name.
- Live on your domain
- Accounts in your name
- Support after launch
- SupportAfter launch
Updates, fixes and changes for as long as the site is live.
- Updates and fixes
- Monitoring
- A number to message
Questions people ask first
With a conversation about what you actually need, and then a written scope with a price against it. Nothing is built until you have agreed both, and that scope is what the work is measured against for the rest of it.
Also under Build
Get in touch
Every one of these reaches us directly, and is answered by a person.