@davemark Personally, I want everything I build to work on both macOS and iOS since if I use it, then my wife will want to use it and she’ll generally be using it from her iPad. So SwiftUI is the preferred option for me most of the time these days.
Went through several Mastodon clients because of this actually 🙂 I liked Mastonaut because the source was available and it was native macOS, but then my wife wanted the features I was building. Looked at at least one which was pure SwiftUI and modified it a bunch but kept hitting issues getting certain things to work — like the UITextView thing I mentioned previously.
Now I’m using a Swift app (with some SwiftUI code) which was mainly written as an iOS app with Catalyst support and I’m modifying the Catalyst part to work for my needs on a Mac. Working out OK so far but it’s a bit of a struggle with Catalyst.
So based on this particular experience, developing for iOS with Catalyst support for macOS would seem to be the the way to go … But my heart is set on trying to get pure native apps on both sides of the fence if I can and so I’d really want it to be SwiftUI cross platform. But that takes a lot more work … and I’m lazy 😛