Mobile app development that ships.
Apps your customers install and your staff depend on, for Android and iPhone from one build, with native code where the hardware needs it. Of our 12 case studies, 7 are mobile, including a venture-backed consumer app, a field app that works with no signal and a till that prints to a Bluetooth receipt printer.
Sound familiar?
We've taken over apps someone else built. The first weeks go into reading the code and stopping the bugs that keep coming back, before adding anything new. That's how Neebu started, and it now ships on a schedule.
When two teams build them, the connection between them is nobody's job, and every bug is the other side's fault. We build both, so that seam is ours to answer for.
The phone in the meeting is newer, faster and better connected than the ones your users carry. An app that assumes good signal fails exactly where the work happens.
How we fix it.
One build, both stores
Built once for Android and iPhone, so a change reaches both stores in the same week instead of being built twice and drifting apart.
Works offline where it matters
Field apps keep working when the signal drops and catch up cleanly when it returns. We've written up how, and why the shortcut version loses data.
Printers, cameras, scanners
Bluetooth receipt printers, cameras and scanners: the fiddly parts that are poorly documented and always underestimated in the quote.
Store releases, handled
We submit to the Play Store and App Store under your own developer accounts, review rejections and staged rollouts included. Nobody on your side has to babysit it.
Where we've done it.
Before you ask.
Flutter or native?
Flutter for almost everything: one build, both stores, cheaper to change. Native Kotlin when the app lives close to the hardware, which is why Cleanter, our Bluetooth printing app, is built that way.
Can you take over an app another vendor built?
Yes, and it's a common way for us to start. Neebu came to us with someone else's code and a launch that had stalled. We read it, stopped the recurring bugs, then got releases moving again.
Do you publish to the Play Store and App Store for us?
Yes, under your own developer accounts, so the listings stay yours. We handle submissions, review rejections and staged rollouts.
Do you keep working on it after launch?
Usually. Most projects start as a fixed-price build and continue as a monthly retainer, because the version that matters is the fifth one, not the first.
Let's make it work.
Tell us what's broken or what you want to build. We'll reply with what we'd make and what it would take.
How we work →