His latest post covers IOS 16, and the outcomes begin predictably. The variety of Apple apps utilizing Swift and SwiftUI continues to develop exponentially, and a number of other current apps have included SwiftUI code for the primary time this 12 months. That mentioned, Goal-C nonetheless dominates the iOS codebase, being a part of over 65% of all binaries, which ought to reply the query of how shut Apple is to deprecating it. Up to now so good.
The stat that gave me pause was that solely 4 Apple apps use the SwiftUI app lifecycle. That is lower than 2% of all of your apps utilizing SwiftUI.
Ought to we learn into this that the SwiftUI lifecycle is dangerous? Is SwiftUI doomed by how few Apple apps use it? In fact not! I feel that is so for a few completely affordable causes. Changing the guts of any app isn’t trivial, except the app is small, and the SwiftUI app lifecycle remains to be new and much from full. But early days for it.
You will need to do not forget that it’s not essential to go “all in” in SwiftUI. Though the famous message from this year’s keynote speechThe quickest and greatest approach to write an iOS app these days is with a combination of applied sciences, and it seems that’s precisely what Apple is doing internally. 🚀
Notice: I do know I’ve used/misused this picture repeatedly. It is value saying that I do not imply to ridicule him, and I do not disagree with the message given the context wherein Josh offered it. The SotU (the place I feel this got here from) is an ideal place for broad statements and setting route. That route is obvious and proper, however the actuality of any firm, be it yours or Apple itself, is way more complicated. Every little thing’s fantastic. 👍