Mickael Romaniello
30 minutes, no slides, nothing to prepare.
Mickael Romaniello
30 minutes, no slides, nothing to prepare.
What changes when the app is for a restaurant, a clinic or a building site.
Many trades still rely on WhatsApp PDFs, Google Forms and voice memos. You don't need "the next Uber" — a simple app is…
02The events industry needs mobile tools that create a direct link with attendees. Here are 3 concrete app ideas to trans…
03An overloaded interface does not reassure your patients — it drives them away. Here is why visual sobriety is the true …
Native or cross-platform, app or website, one platform or two. The decisions that cost the most to change later.
Review, rejections, requirements and the paperwork between a finished app and a published one.
Why people leave an app in the first week, and what keeps them coming back.
What makes an app feel slow, what makes it crash, and how both are measured rather than guessed.
How a budget is built, where the money actually goes, and how scope moves a quote.
Store listings, screenshots and keywords: how people find an app once it is published.
An app is not finished when it ships. What the following year actually involves.
Most of my projects run remotely, and in practice that changes very little. We talk over video whenever you need to, not only at major milestones, and you can reach me with questions at any point during the project — I always answer.
You can also write to me directly on WhatsApp: same number I use every day, a French professional line that works internationally.