Service · Bespoke software

Mobile apps

A mobile app earns its place when people open it often and need what a browser handles badly: the camera for reading a code, the location, a notification that arrives at the right moment, and above all the ability to keep working in a basement with no signal. Think of cleaning staff who clock in at a site and evidence the job with a time-stamped photo; half the buildings they visit have no coverage at all. If a fast mobile site would cover your case, you will hear it in the first conversation rather than six months later.

iOS and Android
phones and tablets
Offline
entries held, then synced
Notifications
targeted, never blanket
Release
under your developer accounts

Where this service reaches

The decision that shapes everything comes first: one shared codebase for both platforms, or two native apps. It sets the budget, the schedule and what the app will be able to do two years from now.

Put your scope to an engineer

Technology choice

Flutter or React Native keep a single codebase across both platforms and usually cost less. Swift and Kotlin win when the hardware has to be pushed hard or when every animation matters.

Journeys and interface

Screens that follow the Apple and Google guidelines, stay readable at large text sizes and work with a screen reader; WCAG 2.1 AA remains the reference. Whether the European Accessibility Act covers your service is a question for your legal adviser, but we design as though it did.

Server and interfaces

The part that holds the data and carries the rules, hosted with OVHcloud, Scaleway or Clever Cloud. We connect it to your business software so the app does not become yet another database to keep current.

Sign-in and payment

Entra ID for internal apps, an email account or Apple and Google sign-in for the public, card payment through Stripe, PayPlug, Lyra or Mollie depending on what your bank supports.

Offline working

Entries are stored on the device and travel up as soon as the network returns, with a written rule for settling clashes. Without it, an engineer in a basement loses half a day of readings.

Publishing and upkeep

Listings, screenshots, the privacy declaration, passing review at Apple and Google, then a release rhythm that holds over the years.

The way an engagement runs

Building a first release depends on the number of screens and on the links to your systems. Store review adds to that, and its length is outside anyone's control, ours included.

01

Usage

Who opens the app, where, at what moment and to do what. This is often where it turns out that several features belong on a desktop screen instead.

02

Prototype on the phone

Clickable screens installed through TestFlight or the Google Play internal test channel, tried in the field before a single feature is built.

03

Iterations

At the end of each iteration a test build your colleagues install on their own phones and use for a fortnight.

04

Release and versions

Published under your company accounts, then kept in step with new releases of iOS and Android at a rhythm agreed in advance.

An app with no upkeep budget carries an expiry date. Apple and Google refresh their systems every year and keep raising what they require of listed apps. Left alone, faults pile up, ratings slide and the app eventually drops out of search results, sometimes out of the store altogether. Treat that line like a hosting subscription: it starts on release day.

Questions and answers

Not always. If people come by twice a year, a fast mobile site serves them better: nothing to install, nothing to update, no review to wait for. An app earns its keep through frequent use, a need for the camera or location, and work without a signal. We settle that question before talking numbers.

Your company's, opened before the first release. For an organisation account Apple asks for a D-U-N-S number, which takes time to obtain, so it pays to start early. An app published under a supplier's account stays with that supplier, ratings and install count included, the day you move on.

Build this with your data protection officer. On our side we confine collection to working hours and a single stated purpose, announce it inside the app and keep retention short. On yours, the processing joins the register, staff are informed and employee representatives consulted where the law requires it. Continuous tracking calls for an impact assessment.

It follows from how many systems the app talks to and how often you change it. The floor is keeping up with new operating system releases and refreshing libraries a few times a year. That work is billed at EUR 95 per hour excl. VAT, or within an agreed monthly allowance if you plan to grow the app.

Where a public body serves citizens, connecting through FranceConnect or France Identité is feasible and we integrate it. For a private company, eligibility depends on the conditions of the scheme itself and we check it at the start. Failing that we stay with an ordinary account and add two-factor authentication where the stakes justify it.

Let us talk about your app

Tell us who will use it, how often and in what conditions. You will get a straight answer: a native app, or a mobile site that costs a fraction of one.

When we are around
Weekdays, 8:00 to 18:00 CET; answers land inside one working day
Talking it through
A call on Teams or Google Meet, whenever writing is not enough

We set strictly necessary cookies only: they keep the site running and remember the city you chose. Nothing here is used for advertising or tracking. More in our privacy policy.