Taking the Veteran Approach to the Next Generation
UIKit has served us for many years with a bright future still ahead of it, and SwiftUI is the cool new kid in town. But which of the two works better when building a real app?
...I’ll answer a question about the future of Storyboards by going through a personal experience of my last 4 years in iOS development.
TL;DR: Flutter is likely to benefit as Apple developers see that they can use the same declarative UI techniques as SwiftUI but also run their code on many more platforms, including Android, Windows, Web, and IOT.
Fixing another common environment issue in SwiftUI.
Why SwiftUI and Combine will help you to build better apps
How to use Swift 5.1 Property Wrappers to cut your dependency injection code in half.
Or how Apple is making a major mistake with SwiftUI…
...Does this mean that your hard-won UIKit knowledge is worthless? Of course not. But SwiftUI is going to make writing professional-looking mobile and watch and desktop apps lot easier. I mean a lot easier.
Some thoughts on SwiftUI view composition, code readability and application performance.
...if you take a look at the SwiftUI examples, you’ll see that almost appear to make no sense at all in current Swift — how the hell can a bunch of seemingly disconnected View properties result in a complete screen?
Join the new SwiftUI language or keep using the affordable Storyboards system?
An explanation of how SwiftUI works coming from a React background