News and media
Newsroom publishing system for a media group with two daily newspapers
We replaced a publisher's patchwork of tools with one news CMS for web, apps and aggregators, live in under a year, then rolled it out to a second daily title.
Build Android and iOS apps for customer orders, bookings, field work and deliveries. Our mobile app development connects the app to your business systems and covers testing and app store submission. We help you choose a shared codebase or native development based on the features your users need.
Driver app
Example
Release 2: proof of delivery
Send release 2 to the app stores?
An example with made-up figures. The buttons send nothing.
Field staff, drivers or customers, and the one job the app has to make easier for them, such as a site report or a repeat order.
A working demo every week, installed on your own phones, so you judge the app by using it, not by reading a status report.
Once your team signs off, we publish it to the App Store and Google Play and connect it to your live systems.
Pick the work that happens away from a desk. Each tab shows how it gets done today and what changes once it lives on a phone.
Engineers and inspectors get the day's jobs on their phone, fill in the checklist on site, add photos and take the customer's signature. The finished report reaches the office without anyone typing up a paper form.
No retypingof paper forms back at the office
Start a projectDrivers see their stops for the day, mark each delivery done and record proof with a photo or a signature. Dispatchers follow progress on screen instead of calling drivers on the road.
Proofof every delivery, on record
Start a projectCustomers order or book from their phone whenever it suits them, and repeat a past order in a few taps. Each one lands in your ERP or booking system directly, so nobody keys it in from an email.
Directinto your system, with no rekeying
Start a projectCustomers follow their order, repair or appointment in your app and get a notification when it moves on. Your team spends less of the day answering the same status calls.
Notifiedthe moment the status changes
Start a projectAn app carries your name onto your customers' phones, so it has to be right. Every app we ship follows these four rules.
Each version goes to a small group of your own staff on test phones first. It goes to the app stores only when the person you name approves it.
The code sits in your own repository, the app is listed under your company's own store accounts, and its data lives in your own cloud account.
The app works from the same records as your ERP, CRM and booking system, so nobody copies data from a phone into the office system. Our team also builds ERPs and booking systems, so we handle the office side of the connection as well.
Every week you see what was finished and what has been spent against the plan. After launch you also see how many people use the app and where it crashes.
Stop after any stage you like. In week three the main screens are already on your own phone, ready to tap through.
Week 1
We go out with the people who will use the app, see where paper and phone calls slow them down and agree on the first release.
You end withA plan and a fixed price.
Weeks 2 to 3
A clickable version of the main screens, on real phones. Your staff or a few customers try it and tell us what gets in their way.
You end withScreens your users have approved.
Weeks 4 to 8
We build the first release for Android and iPhone with a working demo every week, connected to your systems and checked by your IT team.
You end withAn app your IT team has signed off.
Weeks 9 to 10
We publish it to the app stores. One group uses it first, then everyone, and we fix what real use turns up.
You end withAn app in the stores, and a plan for the next release.
After launch we keep the app current as Android and iOS release new versions, or hand it to your team with full documentation. Your choice.
Bring the paper form, phone line or order inbox you want an app to replace. On day five you know what the first release does, who uses it and what it costs, before anyone writes code.
Free, 5 days
Keep the release plan, even if another team builds the app.
From clients in the US, Portugal, New Zealand and the UK.
What buyers ask before an app goes to the stores: price, one app or two, and what happens with no signal.
The choice depends on device features, performance needs, existing code and how much behavior the platforms share. React Native can share substantial application code; native Android or iOS development may suit platform-specific requirements. We scope those tradeoffs before estimating.
The price moves with the number of screens, one shared app or separate Android and iPhone builds, offline working and the systems the app connects to. The free 5-day audit ends with a fixed price for the first release, and you agree to nothing before you see it.
Most business apps work well from one shared codebase in React Native, which means one app to build and keep up. When an app needs more from the phone, such as heavy camera or sensor use, we build natively in Kotlin for Android and Swift for iPhone. The audit tells you which fits, and why.
It can. Field and driver apps can save work on the phone and send it when the signal comes back, so a basement or a rural road does not stop the job. We agree in the audit which screens need to work offline.
Yes. We prepare the store listings and take the app through each store's review, under your company's own developer accounts. An app only your staff use can be handed out privately instead of listed for the public.
Your company does, from the start. The app is listed under your own App Store and Google Play accounts, the code sits in your own code repository and the data in your cloud account, all documented. If we stop working together, you owe nothing extra and we hold nothing back.
The first call is with one of our founders. We share 3 to 4 working hours with the US and UK, keep you updated in your own tools and reply within 4 business hours.
Each one shows what the client needed, what we built and the result, so you can judge how close it is to your own project.
Plain-language notes from our engineers on this kind of work, written for the owner who signs the check.
Free project estimate
Bring the paper form to a 30-minute call with a founder. You leave knowing whether an app fits, whether to build it once or for each phone, and roughly what it would cost. If an app is the wrong fix, you hear it from us.
What you get back
A few lines is plenty. You get a number before any call.