[jamil7]

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.

[edimoldovan]

Can you elaborate on the "The reason is to remove a dependency between your dev team and the target platform."? I think I might not understand your point here.

[jamil7]

If you're heavily or entirely dependent on mobile, then you don't want to be waiting for the React Native/Flutter team to fix critical issues or introduce functionality. You want to remove as many dependencies/parties between your product and your customers.