Your app brief in 5 minutes
Answer about a dozen questions, most of them in one click. You leave with a one-page brief to send to any developer, and the list of what will move their quote. No sign-up required.
Your answers stay in your browser. Nothing is sent to me unless you click "Send me this brief".
Question 1 of 12
In one sentence, what should your app do?
As if you were explaining it to someone who doesn't know your trade.
Why a brief before a quote
A single price for an app is a gamble. Two apps described in the same sentence can have nothing in common once you talk about accounts, payment or network. The brief gives no price: it says what will move it, so every developer starts from the same base and you can compare their answers.
What moves the quote for an app
The ten points the brief picks out from your answers. None of them says a project is too expensive: each says where the time goes.
- 01
Different roles.
Each role has its own screens and rights, and each right is checked on the server: that many more screens to design and test.
- 02
A subscription.
You need to plan for the trial, the failed payment, the plan change and the cancellation, not just the first payment.
- 03
A price calculated by the app.
The calculation rules must be written down in black and white before starting, and the server recalculates the price before every payment: a price changed in the browser must never get through.
- 04
An app to install.
That's two more apps (iPhone and Android), and both Apple and Google review every update before it reaches your users.
- 05
Working offline.
The app keeps the data on the phone, then sends it back when the network returns without losing or overwriting anything: it's one of the trickiest parts of an app.
- 06
Health data.
In France, if it's collected for prevention, diagnosis, care or medico-social follow-up, the law requires an HDS-certified host (article L.1111-8 of the public health code): the hosting choice depends on it.
- 07
Sensitive data or children.
The GDPR forbids sensitive data in principle, except in cases such as explicit consent, and the French data protection authority (CNIL) requires an impact assessment when processing meets several risk criteria, this one included.
- 08
Software to connect.
Everything depends on what it allows from the outside: you need to know early whether it has an entry point for other software (an API), and what it allows.
- 09
Data to bring over.
It's rarely clean: it has to be sorted, de-duplicated and checked before launch.
- 10
A fixed date.
It's what sets the content of the first version: a smaller first version, on time, beats a complete version, late.
What happens to your answers
They stay in your browser, so you can pick up later. Nothing goes to a server while you answer. If you click "Send me this brief", it reaches me by email with your name and address, and you receive a copy. The "Start from scratch" button erases everything.
Questions
- Does the brief commit me to anything?
- No. It's your document: you send it to whoever you want, or to no one.
- Can I send it to another developer?
- Yes, that's what it's for. It describes the need without imposing a technology, and any developer can use it to prepare a first call.
- Why doesn't the brief give a price?
- Because the price depends on the points that weigh, and each one is settled by talking about the project. With me, you then receive a written proposal with a fixed price, before you commit.
- I can't answer some questions. Is that a problem?
- No. Each "I don't know" becomes an open question at the bottom of the brief: that's exactly what a first call is for.
Sources
The sentences on personal data, checked on October 23, 2026.