You are on the home screen
An icon on your users' phone is a permanent reminder no website can offer.
Mobile app development
Your idea finds its place in your users' daily lives.
We define a genuinely useful first version together, you approve the screens before they exist, and we take you through to publication on the stores.
Where you are
An idea for an app, and a lot of unanswered questions.
- You have had the idea for months, without knowing where to start.
- You were quoted six figures and cannot tell whether it is justified.
- You are torn between iPhone, Android or both, and nobody will decide.
- You are afraid of paying for an app nobody will use.
- You do not know what you will keep paying once it is live.
- A developer started, then vanished, and you do not know what exists.
The risk with an app is not technical. It is spending a year building something nobody was waiting for — when a reduced version, out in three months, would have told you straight away.
What changes
What an app brings, when it is genuinely useful.
You can reach them
A notification reaches the people who accepted them, at the moment the information matters.
Use becomes habit
What opens in two seconds gets opened often. That is where an app differs from a site.
It works without signal
Depending on what is planned, the essentials stay available on a train or in an underground car park.
You know what is used
Which screens get opened, which get ignored: enough to decide what comes next on facts.
You start small
A reduced first version can be corrected. A complete app that misses its audience is thrown away.
What we can build
What goes into an app, and what waits for later.
Almost anything is possible. The real question is what must be there in the first version — the rest waits to be asked for by real users.
The basics
- The essential screens
- What a user must be able to do on opening the app, and nothing more.
- iPhone and Android
- One build for both, rather than two projects to fund and maintain.
- Working without signal
- What must stay readable offline, according to what you expect of it.
- Testing on real devices
- Not only on a simulator: on old and recent phones alike.
If your project needs it
- User accounts
- Everyone logs in and finds their own data. Worth planning only if genuinely needed.
- Notifications
- Reaching the people who accepted them, without flooding them.
- In-app payment
- Apple's and Google's rules apply, and so does their commission. We explain that beforehand.
- Connection to your tools
- The app talks to what you already use, rather than creating a second set of records.
Around release
- Publication preparation
- Listings, screenshots, descriptions, answers to the platforms' questions.
- Your developer accounts
- They are created in your name. You remain the owner of the app.
- Test version
- A small circle tries it before everyone else, on their own phones.
- After launch
- The first days' fixes, then the changes decided on real usage.
How we work
We start with what will not go in.
The list of features to leave out of the first version is more useful than the list of dreamt-of ones. It shortens the schedule, lowers the budget, and leaves room for real feedback.
Before / after
From an idea in a notebook to an icon on a phone.
In between: screens you approved, tests on real devices, and a publication prepared without rushing.
What you receive
What is handed over, and who owns it.
The accounts are in your name. The exact list is in the quote before we start.
- The app published on the intended stores, in your name
- Your Apple and Google developer accounts, whose access you keep
- The screens approved before building, on both systems
- A test version you can hand to your testers before release
- The store listings: text, screenshots, answers to the platforms' questions
- The source code of the app, which belongs to you
- A recorded handover session you can watch again
- A written list of the costs that continue after delivery
User accounts, notifications and in-app payment are not automatic: each adds work, rules to follow and sometimes fees. They are decided upfront, and quoted separately.
How it goes
Five steps, and what we need from you at each one.
- 01UnderstandWho the app is for, in what situation it will be opened, and what must happen there first.
- 02ReduceWe agree what goes into the first version and what waits. You approve that list: it sets the budget.
- 03DrawYou walk through the screens before they exist. This is when changing your mind costs nothing.
- 04Build and testWe develop, then hand a test version to your testers. You tell us what snags.
- 05PublishWe prepare the listings, submit, and answer the platforms' questions. Then we stay for the first fixes.
Related expertise
The identity carries through every interface.
One visual system, carried from website to application.
Real apps
Apps you can download today.
TopChrétien, TopKids, Sécuri'Click: they are on the App Store and Google Play, you can install them and judge for yourself.
See the work
Verified Google Reviews
They launched their project — here's what they say
Authentic reviews from clients who saw their website transform their business. No deleted reviews, no filtering.
Thanks to Mitch, not only is he a true pro in his field, but he also understands what we want to achieve and why things aren't working... the functionality of my site is fantastic! It's nothing like my old site... I recommend Mitch without hesitation. A huge thank you!
What can I say? An exceptional experience! I didn't think it was possible to create such a simple, clear, and user-friendly website, especially for the administrators. And above all, a huge thank you to the programmer who was able to adapt to my needs and accommodate all my requests for modifications. Truly bespoke. Incredible. Quite frankly, I've worked with developers on more than five application projects, and they all sold ready-made solutions that they then customized. Here, I feel like my every need was truly listened to, and I got THE website I need. A big thank you. My next projects will definitely be with Shavod!
Professionalism, rigor, meticulous work, execution based on listening to the client, and in line with the latest modern tools are the characteristics I would attribute to Shavod. Florian Forté President of the One Movement Association
A pleasant person who is dedicated to his work, available and responsive, he will satisfy your requests with a smile, joy and good humor.
Very serious. Thoughtful. A good team.
Édouard was responsive, efficient, and helpful in developing my app. He guided me through refining the details I was struggling with. I highly recommend him!
I highly recommend Shavod. George-Michael did an excellent job redesigning our website. He quickly understood our needs, proposed relevant solutions, and delivered work that was professional, efficient, and meticulous. Communication was seamless throughout the project, and the result truly met our expectations. Thank you again for your dedication and expertise!
I had the wonderful opportunity to work with Shavod on my art website. I create paintings and wanted to display them in an online gallery (thais.com). I knew he did good work, but I was truly amazed by the result. He did a fantastic job with the colors. The project was completed in less than a month. Shavod is always easy to communicate with. He listens very carefully to the client, which gave me a great sense of freedom. He's very open-minded, and the possibilities are almost limitless. I highly recommend him.
Thanks to Mitch from Shavod for the JavaScript training! He's a very good teacher, clear and effective. I learned a lot in a short time. I highly recommend him!
Mitch enabled me to quickly develop a prototype IoT application (Bluetooth connection). He is attentive and efficient.
I had the pleasure of working with Shavod on several mobile application projects. His professionalism, proactive approach, team spirit, and excellent attitude make him a trustworthy partner. A true pleasure to collaborate with him!
Shavod created our association's website and smartphone app. He took the time to listen to us and fulfill our wishes. He did a superb job—clean, meticulous, and professional. Perfect.
Budget and timing
What pushes a quote up or down.
What really weighs: the number of screens, whether user accounts are needed, whether the app must connect to an existing system, and in-app payment — the costliest of the four. Count what runs afterwards too: Apple and Google developer accounts are paid, and the platforms impose regular updates on pain of removal. We write those costs into the proposal before you commit.
Estimate my app
Our commitments
What you can count on.
- Developer accounts are created in your name, never in ours
- The source code belongs to you and is handed over
- The costs that continue after delivery are written down before we start
- You see and approve the screens before we build
- We tell you when a requested feature will blow the budget, and why
- No approval date from Apple or Google is promised: it does not depend on us
Frequently asked
What people ask before getting started.
Both, in most cases: we build once for both systems, and the cost difference is small. Picking one is justified when your audience clearly sits on one side — a professional clientele in France leans towards iPhone, a broad public leans towards Android. Look at who you are aiming for before deciding.
That is what we recommend. A reduced version in the hands of real users teaches you in a month what a year of thinking will not. The features left out are not lost: they wait to be asked for, and many never are.
Three of them. The Apple developer account and the Google one, both paid — one yearly, one once. Hosting, if your app stores data. And technical updates: Apple and Google change their rules, and an app that does not follow eventually gets removed. Those amounts are written into the proposal.
You do. We create them in your name and you keep the access. It is worth checking with any provider: if the app is published under the developer's account, you can neither update nor transfer it without them.
Yes, depending on what is planned. Reading content already downloaded works offline without difficulty. Recording an action offline to send later is possible, but takes extra work that has to be quoted. Tell us in what situations your users will be without signal, and we will tell you what that implies.
The build can be planned and held to. Apple's and Google's review cannot: it usually takes a few days, sometimes longer, and can call for changes. Nobody can give you a date for that part — be wary of anyone who does. We prepare the submission so as to reduce the back and forth.
A fix or a new feature goes through the platforms' review, like the first publication. We prepare the update, you approve it, we submit. The rhythm is up to you: some apps change monthly, others twice a year.
That is common, and the two complement each other: the site gets you discovered, the app builds the habit. They are separate services that can share the same visual identity and the same data. Tell us both needs upfront and we will suggest the cheapest order to do them in.