Ummm... you might want to read: Apple: The King is Dead. Long Live the King!

I think the writing is on the wall with SwiftUI.

Regardless of it’s teething problems, it’s destined to be Apple’s primary application development platform, much as Swift has slowly become Apple’s dominant developmental language.

The early Swift years were tough too. Now we use it on every new project and I shudder every time I have to dive back into an Objective-C codebase. There are simply too many things that Swift can do that simply aren’t possible in Objective-C.

I’ve got an iPad Sudoku game I wrote in SwiftUI as a side project that’s almost ready for the app store and while I had to work around a few issues here and there, for the most part things went pretty smoothly.

The biggest thing is that SwiftUI is not UIKit. SwiftUI Views are not UIKit views. They behave in different ways, you have to think differently and you have to implement your architectural patterns differently. It’s… different. ;)

If you stay tuned, I’ve got a major SwiftUI article that should be out in a week or so that goes into some of these things in more detail.

Thanks for reading and thanks for the comments.