Mickael Romaniello
30 minutes, no slides, nothing to prepare.
Mickael Romaniello
30 minutes, no slides, nothing to prepare.
Building apps since 2013. 15+ apps delivered. One dedicated point of contact.
iOS users spend more inside apps than Android users, and Apple's App Store is also the stricter of the two: guideline 4.2 alone rejects anything that is only a repackaged website. I build native iOS apps in Swift that pass review on the first try, using Apple's latest frameworks to deliver the smooth, polished experience iOS users expect.
Book a free call →In short: I build native iOS apps in Swift on Apple's current frameworks, written to pass App Store review the first time — including guideline 4.2, which rejects anything that is only a repackaged website.
Modern Apple-native stack with 60fps animations and buttery-smooth transitions.
First-submission pass rate. I know what Apple reviewers look for.
Deep iOS integration when your product needs it.
Optional but powerful. Universal apps done right.
Apple's privacy rules are strict. Your app will comply by design.
A rejection almost never relates to code quality. The recurring reasons are predictable: a test account that does not work or was never supplied, a permission requested with no written explanation, a feature advertised in the listing but missing from the app, a payment link routing around Apple's system, a privacy policy that does not match what the app does. Guideline 4.2 is the bluntest: an app that is only a repackaged website is rejected. That is prepared before submitting, not after the rejection.
Apple Watch, iPad, widgets, Siri shortcuts: each is another app to design, test and maintain, not a checkbox. It is worth it when the use case genuinely asks for it — a metric checked on the wrist mid-effort, an input tool that gains from an iPad's surface. It is not worth it to show the same thing smaller. I would rather ship one iPhone app that does its job than four variants sharing the same testing budget.
On iOS, tracking a user across apps requires explicit permission, and a large share of people decline — a business model resting on that should know before a line is written. The store privacy label also has to describe exactly what the app collects, including through the third-party libraries added to it. Every permission needs an explanation string, and a vague one gets the app rejected. Better to decide early what you collect: it is also what makes GDPR simple.
Each city has its own dedicated page with insights, case studies, and a contact form.
In 30 minutes, you'll know where to start. No commitment. No technical jargon.
Book a free call →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.
Once we are working together, travelling to meet you on site can absolutely be arranged if your project calls for it. Travel costs are quoted separately, upfront and with no surprises.