Service
Web and mobile applications
Fast, sober interfaces designed for unstable connections and modest phones.
The problem
What we see most often.
Your users give up halfway
The page takes ten seconds to appear, the form empties at the first dropout. Your users go back to the counter, and your platform serves no purpose.
The app is expensive in data
Each visit consumes several megabytes. For a student buying data by the unit, that is a real barrier.
Nothing works on older phones
The app demands a recent model, while most of your users carry a three or four-year-old entry-level Android.
Our answer
Fast, sober interfaces designed for unstable connections and modest phones.
An application designed in Paris or Nairobi assumes a stable connection and a recent handset. In the DRC it becomes unusable: too heavy to load, too expensive in data, unworkable the moment the network wavers.
We build for the opposite. Progressive loading, local caching, forms that lose nothing when the connection drops, interfaces readable on a cheap screen in full sun.
The result is also better on a good connection — restraint has never hurt anyone.
Deliverables
- A progressive web app, installable from the browser, or a native app where the need justifies it
- Mockups of every screen, on mobile, tablet and desktop
- A documented degraded mode: what still works without a connection
- Real testing on an entry-level phone over a 3G connection
- Source code, documentation and release procedure
- Training on administering the application
How it runs
Step by step.
User journeys
We identify the three or four journeys that actually matter, and optimise those before anything else.
Mockups
Mobile first, then widening to desktop. Screen-by-screen approval.
Build
Releases you can test on your own phone from the second week.
Real-world testing
Trials on modest devices and constrained connections, in Kinshasa. Fixes before release.
Our commitment
We do not publish prices. We publish a process.
Every project is different: an honest quote means having understood the need first. Here is what you can count on when you write to us.
The first conversation is free
Scoping, analysing your need and writing the proposal cost you nothing. We start charging when we start producing.
An answer within 48 working hours
Written by someone on the team, not by a robot. And if your request falls outside what we do well, we would rather tell you straight away.
A readable quote within 5 days
Line by line, with the estimated time next to each item. You will know what you are paying for, and why it costs that.
The quote is the price
The signed figure is the invoiced figure. If the scope changes along the way — it often does — we price it and you decide before anything is built.
Frequently asked
What people ask us most.
Native app or web app?
In most cases a progressive web app is enough: installable, usable offline, with no app store and no 40 MB download. We only recommend native when you genuinely need the device hardware.
How much data does a session use?
We aim for under 500 kilobytes on a first visit, and almost nothing afterwards thanks to caching. It is an acceptance criterion, not an intention.
Do you publish to Google Play and the App Store?
Yes, for native apps. We handle the developer accounts, the store listings and the review process.
Does the app work offline?
Partly, and it is documented from the scoping stage: you can read data already loaded, and any input is queued and sent as soon as the network returns.
Let's talk about your project
Tell us where you stand today.
Free first conversation, an answer within 48 working hours, a detailed quote within 5 days.