Catching up with all the post-WWDC podcasts and blog posts, there& #39;s definitely a strong sentiment among developers that the SwiftUI train is leaving the station, and now is the time to get on board

Personally, I won& #39;t be jumping to SwiftUI at this time for simple reasons; I just don& #39;t think I can build what I want to build, at the quality level I want to build it, with SwiftUI, and I don& #39;t think it will be possible for years to come

For some, there is a lot of value in getting in early — SwiftUI will be a competitive advantage for a lot of developers, letting them build complex things in a fraction of the time it takes their peers, and it lowers the barrier to entry for many more

For me, I think the inverse is true; not using SwiftUI will let me build things that it just can& #39;t do. Being so familiar with ObjC & UIKit is my competitive advantage. There may be an intersection point in the future, when time is right for me to switch, but IMO it& #39;s years off

I& #39;m getting *that* little bit closer to adopting Swift in my apps, and I think when that happens I& #39;ll rewrite everything at once. That was my initial plan in 2014 when I wanted to deep-end Swift and use it for everything new; I backed away from that pretty quickly after using it