iOS and Android
One codebase for both stores when it fits, native where the hardware or the performance demands it.
Apps
Mobile app development for iOS and Android
Apps for teams in the field and for your customers, with the backend built alongside. Developed in Paris, published on the stores, source code delivered.
2008 — year we started
Paris 8e — team on site
Source code — delivered, it is yours
The problem
The work happens away from the desk
Technicians, drivers, inspectors and sales teams do the work somewhere else, then type it all in again at the office at seven in the evening. Photographs stay on a phone, signatures stay on paper, and the office learns what happened a day late. A mobile app is worth building when it removes that second entry, not when it simply puts your website in an icon.
We build apps for iOS and Android together with the backend they depend on, because the two decide each other. Screens are designed for one hand, in daylight, sometimes with gloves on: a small number of large targets, few fields, and defaults that are right most of the time. What is not needed in the field does not ship in the app.
Coverage is assumed to be bad. Data is captured offline, queued and synchronised when the signal comes back, with conflicts resolved by rules agreed during scoping rather than by the last person to press save. We publish on the App Store and Google Play under your own accounts, and you receive the source code for the app and the backend.
What you get
What we build into an app
The visible app is half the project. The other half is the backend it talks to.
Works offline
Forms, photos and signatures captured without a signal, queued locally and synchronised when coverage returns.
Backend and API
The server, the database and a documented REST API built with the app, not bolted on afterwards.
Secure sign-in
Token authentication, biometrics, roles per user, remote sign-out, and no shared password on a team device.
Field-ready features
Barcode and QR scanning, geolocation, camera, PDF reports and push notifications when something needs attention.
Store publication
Store listings, review process, phased rollout and updates handled under your own developer accounts.
How we work
How an app project runs
Four stages, in this order. You sign off each one before the next starts.
- 1
Scoping
We follow the job as it is done today, on site. Deliverable: a priced scope, the offline rules and the platform decision.
1 to 2 weeks - 2
Mockups on a real phone
Clickable screens installed on your team's own handsets, so the size of a button is judged where it will be pressed.
2 weeks - 3
Development and test builds
A build every two weeks through TestFlight and Play internal testing, used in the field while we keep building.
8 to 14 weeks - 4
Publication and updates
Store submission, rollout, training, then updates and monitoring. Source code for app and backend is yours.
Ongoing
Technology
What we build with
Picked for what the app has to do in the field:
iOS and AndroidPHP / MySQL backendResponsive web appsDocumented REST APIMariaDBMongoDBRedis (cache, queues)Push notificationsOffline modeToken authenticationGeolocation and barcode scanningStore publication
Example project
A concrete example
Example — to be replaced with a real project
A field app for a team of maintenance technicians
Reports were written on paper, photographed and retyped at the office the next morning. We built an app that captures the job, the photos and the customer signature offline, then pushes everything to the back office the moment a signal is available.
0 re-entry
back at the office
Offline
capture works in a basement
14 weeks
from scoping to the stores
Budget
What a mobile app costs
The figure depends on the number of screens, on offline requirements and on the backend behind it.
Mobile app — from
12 000 €
Indicative figure for a standard scope. Every quote is issued as a fixed price after the scoping phase, with no per-seat fee.
- Scoping and mockups included
- Backend and documented API
- Store submission and rollout
- Source code delivered, no lock-in
How it is priced
An app is priced after scoping
The price depends on the journeys to build, the systems to connect and the fact that two platforms have to be kept working. We scope first, then we put a fixed price on it.
Custom quote
On quote
- Scoping and user journeys
- iOS and Android
- Firm fixed price after the scoping phase
- Publication to the app stores
- Source code handed over
After publication
iOS and Android move twice a year
A published app needs compatibility updates, or it eventually gets pulled from the stores. The contract is priced with the project.
App Care
On quote
No commitment
- Application maintenance
- iOS and Android compatibility updates
- Fixes and monitoring
- Backend maintenance
- Priced together with your project
FAQ
What people ask us most
Native apps or one shared codebase?
One shared codebase for both platforms in most business apps, which cuts the build and the maintenance roughly in half. We go native when the app leans hard on the hardware or on graphics performance. The decision is made at scoping, written down, and it changes the budget rather than the deadline.
Do we need an app, or would a website do?
If nobody works without a signal and you need no camera, scanner or push notification, a responsive website is cheaper and easier to update. We say so when that is the case. An app earns its cost when it removes a second data entry or works where coverage does not.
Who publishes it on the stores?
The app is published under your own Apple and Google developer accounts, so the listing, the reviews and the users stay yours. We set the accounts up with you, prepare the listings and handle the review process, including the rejections that are a normal part of a first submission.
What does it cost to keep an app running?
Budget for at least two maintenance releases a year. Apple and Google change their requirements on their own schedule, and an app left untouched eventually stops being accepted. We quote maintenance separately and yearly, and you are free to have another team do it with the delivered code.
See also
Related services
Let's talk
Tell us what your team does in the field
Thirty minutes is enough to say whether an app is the right answer, and to give you an honest range before anything is designed.