App development
Mobile and web apps that people keep using, built on one codebase where that makes sense.
- Pillar
- Software
- Typical timeline
- 8 to 16 weeks for a first release
- Price
- Quoted in a written scope after the first call
Who it is for
Founders and companies that need an app customers or staff open every day: booking, ordering, field work, or internal tools on the phone.
The problem
Apps fail in the details: slow screens, data lost when the signal drops, a sign-up flow that loses half the people who start it, and a store rejection a week before launch.
What you get
- 01iOS and Android apps (React Native or Flutter) or a web app, chosen for your use case
- 02A backend and API, or integration with the one you already run
- 03Login, push notifications, payments, and analytics wired in
- 04App Store and Google Play submission in your developer accounts
- 05Crash reporting and a release process for updates
How it works
-
Step 1
Scope and flows
We map the screens a user moves through and agree what ships in version one.
-
Step 2
First build on your phone
Early in the project you install a working build on your own device.
-
Step 3
Build in cycles
Weekly builds through TestFlight and the Play internal testing track.
-
Step 4
Release
Store submission, fixes from review, and close watch on crashes after launch.
Timeline
8 to 16 weeks for a first release
A typical range for this kind of work. The written scope we send after the first call sets your actual dates.
Related work
Projects for this service are being written up. See all work
Questions buyers ask
Native or cross-platform?
Cross-platform covers most business apps with one codebase. We go native when the app leans hard on the device, such as heavy camera work or background location, and the scope says so.
What happens after launch?
Apps need updates for new OS versions and store rules. We can keep maintaining it month to month, or hand it to your team with documentation.
Can you take over an app someone else built?
Yes. We start with a short code review, then tell you plainly which parts to keep and which to rebuild.
Tell us what you are trying to build
A 30-minute call. You explain the problem, we ask questions, and you leave knowing whether we are the right team and what the work would involve.