If most of my focus is on Apple platforms (iOS, macOS, tvOS, watchOS, and possibly soon the rumored arOS), I would rather pick SwiftUI over any other framework.
Though at its early stage, as with all new Apple tech, you will still be losing your hair. Hopefully there's only a few months to go until a substantial increase in its stability (and documentation.)
The issue with SwiftUI is that you can't just have "most" of your focus on Apple platforms. You need to have _all_ of the focus on Apple platforms because you can't run it anywhere else.
With Flutter you have all of your focus on most of of the smartphone market practically for free which makes a massive difference in your addressable market.
Yea, if you are Apple only; go for SwiftUI... but who can afford to be Apple only?
I think there are a billion apps that no one cares about because developers have forgot about trying to solve actual problems in favor of “we have an app”.
For us, it was “learn once, write anywhere” for react, or “write once and actually use everywhere” for Flutter. Native wasn’t even a question for the size of the team on this latest project.
We make money by solving problems; not launching some app built with some language
Though at its early stage, as with all new Apple tech, you will still be losing your hair. Hopefully there's only a few months to go until a substantial increase in its stability (and documentation.)