4 ms·
I always encourage native. I think it basically depends what you need to build, the cross platform toolkits can work well for pushing out a mobile client for an
by jamil7 6y ago
I always encourage native. I think it basically depends what you need to build, the cross platform toolkits can work well for pushing out a mobile client for an existing service or if you just need a presence in the respective stores. Keep in mind not everything is easier / faster with cross platform, some things can be a lot more painful, especially if you want to take advantage of platform specific features or hardware. Also Kotlin Native / Multiplatform is great, I'm a convert. It's not really comparable to the others however since the focus is on building shared libraries and frameworks, you still need to bring your own UI.
- _448 6y ago> It's not really comparable to the others however since the focus is on building shared libraries and frameworks, you still need to bring your own UI. So it will be Kotlin for business logic and Flutter for UI?
- jamil7 6y ago> So it will be Kotlin for business logic and Flutter for UI? It is possible, I've heard of it being done by others but I don't have a huge amount of experience with Flutter and last time I looked interop was a bit tedious in Flutter. I'm also not sure if you would gain all that much from using Kotlin in that case, rather keep everything in Dart / Flutter? In the case of the last contracting job I did I used native UI frameworks from Android and iOS with a shared Kotlin framework doing business logic. Depending on your use case and experience (and if you have time for it) I'd encourage building some small tests or proof of concepts in each option and evaluate.