Consideration to make SwiftUI a library independent to the system version like Swift before?

We hope that SwiftUI can be a standalone library which is similar to Swift (before 5), Jetpack or AppCompat library.

If it is bundled in iOS / macOS, we cannot use it for production for at least one year since it’s far from mature now.

Accepted Reply

SwiftUI is a standalone library now. It lives in /System/Library/Frameworks/SwiftUI.framework, and is dynamically linked like any other framework, with the stable Swift v5 ABI.


Or do you mean that it would be available in some format that you can include in your application bundle as a dependency? That's highly unlikely, given that it's very dependent on particular versions of the operating system's other libraries; there's going to be some special sauce inside UIKit, and SwiftUI also links directly against CoreUI, which is the private framework that handles 'theme' rendering, i.e. the look & feel of buttons, bars, etc. on each platform.


Rest assured, though, that the pace of improvement will be brisk. Of all the teams at Apple, that one has some of the absolute best & brightest working on it. There are some rough edges right now, but most can be circumvented in one way or another, plus you can adopt it piecemeal via UIHostingController and friends—implement a modal controller's content in SwiftUI, or a single tab in a UITabView, and keep the rest as-is.

Replies

SwiftUI is a standalone library now. It lives in /System/Library/Frameworks/SwiftUI.framework, and is dynamically linked like any other framework, with the stable Swift v5 ABI.


Or do you mean that it would be available in some format that you can include in your application bundle as a dependency? That's highly unlikely, given that it's very dependent on particular versions of the operating system's other libraries; there's going to be some special sauce inside UIKit, and SwiftUI also links directly against CoreUI, which is the private framework that handles 'theme' rendering, i.e. the look & feel of buttons, bars, etc. on each platform.


Rest assured, though, that the pace of improvement will be brisk. Of all the teams at Apple, that one has some of the absolute best & brightest working on it. There are some rough edges right now, but most can be circumvented in one way or another, plus you can adopt it piecemeal via UIHostingController and friends—implement a modal controller's content in SwiftUI, or a single tab in a UITabView, and keep the rest as-is.