To be honest, I never liked hybrid frameworks. In that time I’ve also played with iOS and I know the basics and how to build a simple but functional app, and occasionally I’ve tried out Flutter and Xamarin. I’ve been developing Android native apps for 4 years now, if I count my time as a student. Now let’s see my experience using this framework in a professional environment and what are some of the pros and cons that I’ve found along the way. If you want, you can write the entire architecture in KMM of each app up until the UI, which is where usually the biggest hit in performance happens in the other hybrid technologies. With this framework, there is a codebase in Kotlin that is shared between iOS and Android. KMM approaches these problems differently. Paying independent teams to develop an app for each platform is more expensive than paying for a hybrid implementation.Ĭlients that pay less money usually implies lower salaries, and probably worse backend as because of this money limitations, deteriorating the coding experience and the final product result. Performance can take an impact, usually as the apps grows, access to specific things of each platform is harder compared to native development and there’s also the money department, let me explain. This of course seems too good to be true, but as it happens to everything in life, there are trade-offs. In the current space, we already had React Native, Xamarin or Flutter, where the developer with just one codebase could release a mobile app for iOS, Android and even the web. Today I want to share with you my experience after 6 months using it in a professional app. Kotlin Multiplatform Mobile (from now on, KMM), it’s a new framework to develop hybrid mobile apps.

Kotlin multiplatform ios example