Ask HN: Native App Development Stack

You have to introduce ordering in your KPIs. If developer experience is more important, then you can get better results with cross platform. If user experience is more important, then you are virtually guaranteed to get better results with native. Personally I’m of the opinion that user experience should never be subordinate to developer experience, so at least for me the choice is clear: native.

Also consider whether you will benefit from a broad install base, i.e. when building a social app, or if you can go for one platform first. Lastly, I’d consider the stage your in, i.e, are you trying to find product market fit or not.

If native stills feels like a lot of extra work, I’d suggest building a common core, in e.g. Rust, to share non-UI code between the platforms.

This is hard to answer without knowing what kind of business you're building. A rough rule of thumb which I've said before is, if your business is highly or entirely dependant on mobile (often B2C apps) then go native and build for whichever platform is dominant in your region/industry first. The reason is to remove a dependency between your dev team and the target platform. The project I'm on right now went with SwiftUI/Jetpack Compose, I would use SwiftUI only if you can target the latest OS and stay far away from it on macOS. I haven't used it for a while but I've heard React Native has also gotten a lot better lately.

SwiftUI/Swift and Jetpack Compose/Kotlin for us - despite using react for other stuff, we find these native languages to be very nice to use and productive. Also, if you’re targeting a featured by Apple badge using their native technology is a huge plus vs react native.