Mobile Apps en Lyon
How we work in Lyon
The first phase may not be an app at all
If what needs checking is whether your people will use the service from a phone, a website built properly for small screens checks it in weeks, with no developer accounts or store reviews in the way. When the case calls for the camera, notifications or offline work, then you do need an app.
Short, but with the whole journey in it
An application can have three screens and be finished, but it cannot leave the user halfway through a flow. In the first release we cut features, never steps: whoever comes in has to be able to start and finish what they came for, even if that is one single thing.
Every release inherits the previous one's users
Unlike a website, the old version stays installed on phones that nobody updates. Each phase has to live alongside the one before it: data that migrates, servers answering both. That is a real cost of working in phases and it goes into the budget instead of turning up as a surprise.
The recurring costs start in the first phase
From the moment there is a published release there is maintenance: operating systems that change, dependencies that expire, stores that tighten their requirements. Counting that from the first phase avoids the second-year surprise, when the app stops building and nobody had set aside a budget to touch it.
Answering your questions
What people ask us about Mobile Apps in Lyon.
If your question is not here, tell us about the project and we will answer with real context.
Ask us directlyReal work
Projects we have built
Full service · All the detail
Mobile Apps: stack, process, use cases and FAQs