Mickael Romaniello
30 minutes, no slides, nothing to prepare.
Mickael Romaniello
30 minutes, no slides, nothing to prepare.
Native or cross-platform, app or website, one platform or two. The decisions that cost the most to change later.
Sharing code between a desktop app and its browser version does not halve the work. Here is what the second platform ac…
02An app that's just a website wrapped inside an app. That's exactly what triggers tons of Apple 4.2 rejections.
03Even the best apps in the world have flaws. The real danger isn't imperfection — it's never listening, never shipping.
04"This app would like to access your location." Today, tons of users get suspicious right at this moment. Logical.
05"Yeah but that's just a small bug." Extremely dangerous sentence. Because a small technical bug can become a huge trust…
06"It's a bit like Uber… but for hairdressers." Not bad to explain a concept. Catastrophic when you copy without understa…
07Good UX is not only about making an app "beautiful". It is also about reducing the user's anxiety.
08Template-based apps look cheap because they are cheap — in every sense of the word. Here's the honest comparison betwee…
09Some of the most successful companies did not start with a mobile app. They discovered one was needed when their busine…
10Uber Eats, Deliveroo, DoorDash — these apps didn't win on price or restaurant selection. They won on user experience de…
11Testing on a simulator catches maybe 30% of real issues. The rest only surface when actual users, on actual devices, in…
12Google Play changes its rules without warning, rejects apps without clear reasons, and enforces update deadlines in 30 …
13Bugs are inevitable. The real question is how you handle them. A well-managed bug can actually strengthen user trust.
14The most common mistakes that turn a good idea into a failure. Lessons from 12 years of building apps.
15The most common mistake is wanting an app just to follow a trend. Discover why and how to create a mobile application t…
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.
What changes when the app is for a restaurant, a clinic or a building site.
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.