Trois surfaces numériques de tailles différentes reliées par un même ruban de lumière cyan.

Product & software

Mobile and desktop application development

An application only makes sense if it does better than a website on the same subject. Notification, offline use, sensors, a daily workstation: if none of these reasons apply, we will say so before building it.

Start a project See the work

Expertise: Product & software
Platforms: iOS · Android · macOS · Windows
Approach: Native or cross-platform, from the use
Scope: Design · development · publishing
Operations: Updates, crash follow-up, stores

01 / 05

Native, cross-platform, or web?

Native gives full access to the platform, the best performance, and the finest system integration. On mobile it costs two codebases.

Cross-platform shares one base between iOS and Android, which splits the cost and speeds evolution. It hits its limits on heavy graphics and deep system integrations.

An installable web app — PWA — removes the stores and their review cycle. It fits many internal tools and fails where you need reliable iOS notifications or hardware.

That choice is made at scoping, on use and budget, not on technical preference. It is the first decision that really commits you.

02 / 05

What makes an application kept

01
Startup
A slow-to-open app is an uninstalled app. Time to a useful first paint is a design constraint, not a late optimisation.
02
Offline
The network drops: on the move, underground, on a site. An app that needs a connection to show what it already downloaded betrays its user at the wrong moment.
03
Notifications
That is often the real reason an app exists. They must be relevant, configurable, and rare. One notification too many and the user turns them all off.
04
Updates
An app lives for years on systems that change every year. The foundation must let you follow iOS and Android versions without a rewrite.
05
Publishing
Developer accounts, store listings, screenshots, privacy, Apple review, staged rollout. We take that chain — it blocks more projects than people think.
06
Measurement
Crash reports, installed versions, journeys actually taken. Without instrumentation, an app is a black box you cannot tell is useful.

03 / 05

The cases where an application is truly justified

A field team that captures data away from the office, often without network.
A service used every day, where every second of opening counts.
A product that needs to notify at the right moment, not wait for a visit.
A desktop workstation that handles local files or hardware.
An internal tool that must run on rugged tablets or dedicated hardware.

04 / 05

What we get asked most

The answers we give anyway at the first conversation.

Do you really need an app, or is a site enough?

In most cases, a fast, well-designed site or a web application is enough and costs far less to maintain. An app is justified by offline use, notifications, hardware access, or intensive daily use. We settle that question at scoping, honestly.

What does application development cost?

Cost depends mainly on the number of platforms and how deep the features go. A cross-platform base reduces the bill substantially. Plan also for yearly operations: developer accounts, compatibility updates, fixes.

Who publishes the app on the stores?

We prepare and submit, but the Apple and Google developer accounts are opened in your name. That is essential: your app, your reviews, and your users must not depend on a vendor's account.

What happens after launch?

Systems evolve every year and stores require regular upgrades. We offer follow-up that covers compatibility, fixes, and evolution, at a rhythm fitted to real use.