Is Kotlin Multiplatform Right for Your App?

Hey guys and welcome back to a new video. You are maybe building some app or you're maybe planning to build an app and when building an app there are a gazillion different ways how you could achieve that. You could build two separate native apps for iOS and Android. You could use crossplatform framework like flatter or like react

framework like flatter or like react native or you could use something like cotton multiplatform. If you maybe already following me for a while then that cotton multiplatform is definitely a thing that I'm focused on because my channel is all about cotton. But still, I would not generally recommend Carter multiplatform, but only if some of certain scenarios apply to

if some of certain scenarios apply to your situation. And in this video, I will go over the exact scenarios where I would say definitely build your app on Carter multiplatform, but I will also go over the scenarios where I think it's maybe not the right pick for you. And I will keep myself very short. So, let's dive right into it. Scenario number one

dive right into it. Scenario number one is you already tried Cotlin as a programming language and you just like it obviously because Scotland multiplatform is in the end the only cross or multiplatform framework that allows you to build apps for all platforms with cotlin and I always say if a developer really truly enjoys the

if a developer really truly enjoys the work they are doing then that alone will yield a better result than working with a technology you don't enjoy that much. Scenario number two and here we really get to the most important advantages cotton multiplatform has over all these other crossplatform frameworks like flutter and react native. You are a

flutter and react native. You are a native Android developer or you work in a team of native Android developers. If that is the scenario you find yourself in. So if you understand native Android development with Kotlin, then building your first apps for iOS as well with Cotlin multiplatform takes you maybe one

Cotlin multiplatform takes you maybe one to two weeks of adoption because if you think about it, you are using the same language, you are using the same IDE the same paradigms to build carton multiplatform apps that you also use for a native Android development and possibly even the same UI framework

possibly even the same UI framework Jetack compose. Really, the only learning curve here comes from the different project structure a Carton multiplatform project has. And in my experience, you can really just perfectly learn that on the fly when needing it. So for example, you notice during development, hey, I need to show a notification on the iOS side. Then that is the point where you can

Then that is the point where you can just dive into that, ask AI, research a bit and with that knowledge, you can implement that fairly easily in your carton multiplatform project. But other than that, if you are already familiar with native development, the learning curve for KMP is super small compared to technologies like Flutter or React

technologies like Flutter or React Native where you would maybe have to learn a completely new technology from scratch that has different paradigms that uses different ideas and is built around different ideas. And this is also what I think is really the biggest advantage here of Carter multiplatform that there's already such a large group of developers. So all the native Android

of developers. So all the native Android developers who can suddenly build native iOS apps with it as well without having to learn any complex other topics they aren't already familiar with. Scenario number three where I would definitely recommend cotton multiplatform is you have an existing native Android app and