kmm-production-sample VS react-native

Business logic is not only about backend. Apps usually have a lot of client-side logic that can be written once in KMM and used on both platforms. See [1] for a high level architecture diagram.

I'm an iOS dev and I've been using KMM on a couple of projects for more than a year now. It's really a powerfull technology which allows teams to move faster, but there are downsides, for example lack of native Swift interop, though there are opensource tools trying to solve this [2].

[1]: https://github.com/Kotlin/kmm-production-sample/tree/master#...

I'm an Android dev for 10+ years and I've decided to give a go with Kotlin Mobile Multiplatform to try iOS development as well. For that purpose I would need a Mac obviously, and Windows 11's flaws don't help either so I made my mind and I would like to pick a Mac as my next developer machine for the next 4-5 years.

I don't use iOS, but https://kotlinlang.org/lp/mobile/ claims that using Kotlin works on iOS too. You still will need a Mac though, but that's pretty much a given if you want to develop iOS apps.

Kotlin Multiplatform with Realm as a middle layer.

Kotlin Multiplatform. You write the UI fully native for each platform, but have all the business logic as shared code.

maybe people confused it with kotlin multiplatform mobile which indeed support ios but only the business logic. you have to write the ui in swiftui.

I think the most compeling use for Kotlin Native is mobile. I wonder if it's possible to write a Kotlin multi-platform library that can then be used from the JVM, JS, iOS and Android? What would such library look like from the other languages? This is something I am trying to find out right now, and Kotlin Multiplatform seems to be the only sane choice to do this (but I am not sure yet that it's actually good/possible right now). Any more information about this would be appreciated.

Kotlin isn't just JVM and Kotlin projects like this one for writing iOS+Android apps look quite promising: https://kotlinlang.org/lp/mobile/

This is a modified version of the file from the react native cli template

Recently, there has been a notable shift in mobile application development practices. Rather than creating separate applications for each native platform, many developers are opting for hybrid mobile frameworks like React Native.

React Native [ https://reactnative.dev/ ]

Versatility: JavaScript is not limited to web browsers. It's used in a variety of environments, including mobile app development (using frameworks like React Native), game development (using libraries like Phaser), and even serverless computing (using platforms like AWS Lambda).

In the competitive landscape of mobile app development, user experience (UX) has emerged as a critical differentiator. React Native, with its robust framework and versatile capabilities, offers developers a powerful toolkit to create seamless and engaging user experiences. This blog post delves into the design principles and best practices in React Native app development, uncovering how developers can elevate user experience to new heights and drive success in the digital realm.

You can find the React Native documentation here and Flutter Documentation here.

Additionally, React Native, an extension of React.js, enables developers to create hybrid mobile applications with ease.

You don’t know what to do with your time while applying the 5th rule? Start small, tiny steps. If you can’t read much, start small, 15 minutes a day reading a technical article or even a book like Effective Java, by Joshua Bloch. You don’t like to read? Create small projects by using a framework you want to learn. Check for example: React framework.

React Native: A framework for building native apps using JavaScript, sharing logic code while retaining native performance.