kmm-production-sample VS dioxus

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/

We have a web components example here: https://github.com/DioxusLabs/dioxus/blob/fd21c971038840130f...

Everything should work like normal except: attributes are not typed, custom event listeners must be implemented with web-sys

I think something like https://dioxuslabs.com could deliver native, cross platform apps and win back mobile.

While we took an in-depth look at Dioxus in this tutorial, there is still so much to learn. Luckily, Dioxus provides detailed documentation with references and cookbooks to guide developers. Make sure you check it out, and feel free to comment below with any questions.

You can probably imagine the challenges of integrating such a system in a robust way that does a good job and improves on the status quo. We felt like the Tauri implementation worked well for Tauri apps. But there’s a problem: it was so tightly coupled to Tauri that the work couldn’t be enjoyed by other projects (not even the ones like Dioxus who were using Tauri’s underlying technology of Tao + Wry).

Floneum is a graph editor for local AI workflows. It uses llm to run large language models locally, egui, and dioxus for the frontend, and wasmtime for the plugin system. If you are interested in the project, consider joining the discord, or building a plugin for Floneum in rust using WASI