React worked because it was a layer over what developers already knew (DOM elements like divs/anchors/etc) that simplified what they were already doing.
SwiftUI simplifies what devs already do (modify UI in response to state), but it also adds a wholly new set of components instead of AppKit/UIKit (and bridging is not super fun).
Most of my trouble with #SwiftUI seems to come from the latter half (new components/bridging), and none of the former. Maybe a React-y AppKit would be better for me.
@stevestreza I will say that the person I know who’s had the most success getting SwiftUI to do what she wants isn’t an engineer at all, but rather Pocket’s Head of Design. SwiftUI is as much she knows, and she loves it.
@stevestreza I’ll for sure let him know. 😁
@nicole I've seen people do some awesome things with it for sure, especially on iPhone. My problems usually end up in the more fiddly bits of interaction design. And the Mac parts tend to be less supported.
(Also if Matt is still in charge of things over there, tell him hi for me, and I hope y'all excised all my old code out by now 😊)