SwiftUI vs. UIKit SwiftUI is a declarative UI framework. You use it to build User Interfaces (UIs) for Apple platforms, including iOS, macOS and iPadOS. SwiftUI’s approach to building UIs completely consists of writing Swift code, which is incredibly productive. A central concept in SwiftUI is that “state drives the UI”. Your app’s UIs are a result of state. You can manipulate state, and connect it to your apps UIs, with tools like property wrappers and Combine. Here’s a quick example of a view built with SwiftUI: struct BookList: View { @ObservedObject var viewModel: BooksViewModel var body: some View { NavigationView { List(viewModel.books) { book in NavigationLink(destination: BookEdit(book: )) { BookRow(book: book) } } .navigationBarTitle(“Books”) .onAppear { viewModel.fetchBooks() } } } } SwiftUI was launched during WWDC in 2019, so it’s a relatively new technology. Since its inception, SwiftUI has received several improvements. Most notable, the “SwiftUI 2.0” iteration (2020) – and many developers have high hopes for WWDC 2021. Take for example the MapKit framework, which is used to display interactive (geographic) maps in apps. SwiftUI didn’t have a Map view at its inception in 2019, but you could still use a native MKMapView by reusing it from UIKit. The fact that you can use UIKit-based views in SwiftUI has greatly helped its adoption. In 2020, a native Map view has been added to SwiftUI and MapKit. You don’t need to use MKMapView anymore, and instead can use the new Map view right out-of-the-box. It’s worth noting that the new Map view has fewer features than its UIKit counterpart. This story about MapKit and SwiftUI is a good illustration of what to expect of SwiftUI in the future. We’re going to see that SwiftUI gets extended more and more, until it’s (hopefully) comprehensive and mature enough to replace UIKit.