Apple has historically not cared about mid-level companies and above, and SwiftUI is just another example of that. Everything they do is geared towards absolute beginners / very simple projects, even Xcode itself becomes basically useless once you reach a certain level of complexity. I don't understand why they do that.
> Apple has historically not cared about mid-level companies and above
I wouldn't say that. I've worked for a couple of marquee corporations that did a lot of work with Apple.
They do things like assign direct contacts to larger corps. They don't really rely on their "popular" culture docs to support bigger companies.
It's pretty natural to use their popular front as an "onboarding" system for smaller acts, with the plan to integrate them more tightly, if they get successful enough.
That said, their App Store is quite restrictive, and can be a big fat pain to deal with; even as a bigger corporation.
Quite doable, though. I've released over 20 apps to the iOS/Mac App stores, over the last dozen years.
Source? I haven't heard of any large company with complex projects fully adopting SwiftUI in their main product and not immediately regretting it. Successful adoption seems to be achieved only if the product is really simple or when using it in a very specific / isolated place of their main product (also simple). Everything else is UIKit because SwiftUI sucks at complicated logic.
