
Soonish, the first iPhone launch will complete 20 years. Since then, the world has changed forever. Fast forward to our present days, the question about what Mobile means in terms of product distribution and how to ace a great Mobile presence with efficient Engineering still remains, in particular because how much field changed and evolved in the past decade.
I've seen the situation many, many times : leadership just decided to create a Mobile-first product, and the Engineering Leader faces the question:
Which technologies should I propose?
Then the research starts, and the more one follows the rabbit hole, the more the frustration grows.
After all, Mobile is much more closer to the Desktop than the Web; the walled-gardens of Google Play and Apple App Store are a compliance nightmare, and represent a far-from-simple entry barrier.
Mobile/Native stack are a real Engineering pain from multiple perspective, and although hybrid options exist, there is no clear path on how to achieve a real mix of available technologies in order to achieve a sustainable Mobile strategy in the long run. And for mature products, the pain is also present, because for lots and lots of Mobile/Native teams out there are just too unhappy and too afraid to jump into existing solutions for sharing code.
I'm here to help you with that. Stopping being dragged by all buzzwords echoed in the chambers of solution providers, and learn from the trenches about what few people talk about.
Kotlin Multiplatform? Great, but perhaps the monorepo price is too expensive to share just 15% of code... On top of that: have you ever asked iOS folks about? Can we even monitor errors in decent way?
React Native? Great, but have you ever wondered that a Native Shell alongside with a Mobile/Web Core could be simpler and faster?
Flutter? Have you been following the ecosystem recently?
Cross-platform shared code? Yes, that is possible on Mobile, too. No, that is not KMP, Flutter or React Native.
Bring your use case. Tell me about your short and mid term vision, share your constraints, and let me share what I'd do if I was on your shoes, with your budget and your timeline.
Most importantly : I'll tell you why I'd do that, and put all the unspoken trade-offs in the picture, so you can make your best informed decision.