Tag: ObservableObject

Observing a KVO compatible model in SwiftUI and MVVM

Post author By Toomas Vahter
Post date November 8, 2020
No Comments on Observing a KVO compatible model in SwiftUI and MVVM

In model-view-view model (MVVM) architecture the view model observes the model and provides data for the view by transforming it when needed. When the user interacts with the view and changes the data in it then the view model’s responsibility is to propagate those mutations back to the model object. Therefore, the important part in MVVM is how to manage data flows between objects. This time we’ll take a look on observing key-value observing (KVO) compatible model objects with Combine framework in SwiftUI view. The example view what we’ll build looks like this:

SwiftUI view with text fields for setting first name, last name, and street address. Under that is a label with recipient, postal address, and package contents descriptions. Under that is a button for adding more items to the package. — SwiftUI view which enables editing package related information and displays a summary of the package.

Model layer

The model object represents a package which contains information about the recipient, the sender, and the contents. The recipient and the sender are represented by a Person object which includes a first name, a last name, and a postal address. The contents is an array of immutable PackageContent objects. In Swift, we can use KVO by specifying @objc and dynamic modifiers on properties. Dynamic means that method dispatch is using objective-c runtime and therefore all the types must be representable in objective-c runtime. This immediately adds restrictions to the types we can use. When writing pure Swift code I do not recommend using KVO but sometimes we just need to use it. One example is NSManagedObject from the CoreData framework. But in this app we are not dealing with NSManagedObject but with a simple NSObject subclass instead.

	final class Package: NSObject {
	@objc dynamic var recipient = Person()
	@objc dynamic var sender = Person()
	@objc dynamic var contents = [PackageContent]()
	}

	final class Person: NSObject {
	@objc dynamic var firstName: String = ""
	@objc dynamic var lastName: String = ""
	@objc dynamic var postalAddress = CNPostalAddress()
	}

	final class PackageContent: NSObject {
	init(title: String, weight: Int) {
	self.title = title
	self.weight = weight
	}

	let title: String
	let weight: Int
	}

view raw PackageKVO.swift hosted with ❤ by GitHub

KVO compatible model object.

View Layer

The view object is responsible for describing the UI and rendering data represented by the view model. We have a simple form for modifying the recipient’s first name, last name, and the street name (for keeping this UI simple I left out all the other postal address related properties). At the bottom of the view we have a text object which just describes the package and a button for adding new items to the package’s contents. Whenever any of the package’s properties change, the view needs to reload. View reload is done through the @StateObject property wrapper (read mode about observing view models in MVVM in SwiftUI and @StateObject and MVVM in SwiftUI).

	struct ContentView: View {
	@StateObject var viewModel = ViewModel(package: .makeExample())

	var body: some View {
	ScrollView {
	VStack(spacing: 16) {
	Text("Recipient")
	.font(.headline)
	InputView(title: "First name",
	value: $viewModel.recipientFirstName)
	InputView(title: "Last name",
	value: $viewModel.recipientLastName)
	Text("Address")
	.font(.headline)
	InputView(title: "Street",
	placeholder: "e.g. 37 Christie St",
	value: viewModel.street)
	Text("Summary")
	.font(.headline)
	Text(viewModel.summary)
	.frame(maxWidth: .infinity, alignment: .leading)
	Button("Add item", action: viewModel.addRandomItem)
	}
	.padding()
	}
	}
	}

view raw ContentView.swift hosted with ❤ by GitHub

View Model layer

The view model’s responsibility is to observe the model object and propagating view changes to the model. It acts as a transformation layer where we can transform any data in the model to anything suitable for displaying. In the example below we are reading CNPostalAddress and only returning street name and reading multiple properties and returning a summary string. View models make it easy to contain such logic and also make it more easy to test.

Foundation framework defines a publisher named NSObject.KeyValueObservingPublisher which can be used for observing KVO compatible properties. One of the approaches is to use this publisher and then bind the model changes to the view model’s own property. Combine framework provides a convenient assign operator which takes a target publisher as an argument. Convenient because we can connect it with @Published properties in the view model. @Published properties automatically notify the ObservableObject’s objectWillChange publisher which is observed by a SwiftUI view. As soon as the property changes, SwiftUI view picks up the change and reloads itself. Note that we’ll also need to propagate changes back to the model when user updates the view and therfore the @Published property. This can be achieved by connecting property’s publisher with dropFirst, removeDuplicates and assign publishers where the latter assigns the value to the model object. Drop first is used for ignoring the initial value of the property. One downside is that now we can have the same information both in the view model and in the model. But on the other hand it makes the data streams easy to read and no need to have extra observation for triggering the view reload by manually calling send() on the objectWillChange publisher.

	@Published var recipientFirstName: String = ""

	// Model -> View Model
	package.recipient.publisher(for: \.firstName)
	.assign(to: &$recipientFirstName)

	// View Model -> Model
	$recipientFirstName.dropFirst()
	.removeDuplicates()
	.assign(to: \.firstName, on: package.recipient)
	.store(in: &cancellables)

view raw ViewModel.swift hosted with ❤ by GitHub

Observing model and view changes.

Another approach what we can use is providing properties in the view model which return a Binding. This allows us to write the transformation code inside the get and set closures. This is what we have done with the street property. Note that we’ll still need to observe the model as the model can change at any point. Binding just provides a way of accessing the value. Therefore, we’ll need to set up an observation and calling send() on the objectWillChange publisher.

	// Observing changes
	package.recipient.publisher(for: \.postalAddress)
	.notifyObjectWillChange(objectWillChange)
	.store(in: &cancellables)

	// Providing a binding for the view
	var street: Binding<String> {
	let package = self.package
	return Binding<String>(
	get: {
	package.recipient.postalAddress.street
	},
	set: { newValue in
	let postalAddress = package.recipient.postalAddress.mutableCopy() as! CNMutablePostalAddress
	postalAddress.street = newValue
	package.recipient.postalAddress = postalAddress
	}
	)
	}

	extension Publisher where Self.Failure == Never {
	public func notifyObjectWillChange(_ objectWillChange: ObservableObjectPublisher) -> AnyCancellable {
	return self.sink { _ in
	objectWillChange.send()
	}
	}
	}

view raw ViewModel.swift hosted with ❤ by GitHub

Providing a binding for the view.

If we go back to the SwiftUI view and connect all the properties then the full implementation of the view model looks like this:

	extension ContentView {
	final class ViewModel: ObservableObject {
	private let package: Package
	private var cancellables = [AnyCancellable]()

	init(package: Package) {
	self.package = package

	// Model -> View Model
	package.recipient.publisher(for: \.firstName)
	.assign(to: &$recipientFirstName)
	package.recipient.publisher(for: \.lastName)
	.assign(to: &$recipientLastName)

	package.recipient.publisher(for: \.postalAddress)
	.notifyObjectWillChange(objectWillChange)
	.store(in: &cancellables)
	package.publisher(for: \.contents)
	.notifyObjectWillChange(objectWillChange)
	.store(in: &cancellables)

	// View Model -> Model
	$recipientFirstName.dropFirst()
	.removeDuplicates()
	.assign(to: \.firstName, on: package.recipient)
	.store(in: &cancellables)
	$recipientLastName.dropFirst()
	.removeDuplicates()
	.assign(to: \.lastName, on: package.recipient)
	.store(in: &cancellables)
	}

	// Example of using published property
	@Published var recipientFirstName: String = ""
	@Published var recipientLastName: String = ""

	// Example of using bindings for propagating values
	var street: Binding<String> {
	let package = self.package
	return Binding<String>(
	get: {
	package.recipient.postalAddress.street
	},
	set: { newValue in
	let postalAddress = package.recipient.postalAddress.mutableCopy() as! CNMutablePostalAddress
	postalAddress.street = newValue
	package.recipient.postalAddress = postalAddress
	}
	)
	}

	var summary: String {
	let contents = package.contents
	.map({ "\($0.title) \($0.weight)" })
	.joined(separator: ", ")
	return """
	Recipient: \(package.recipient.firstName) \(package.recipient.lastName)
	Postal address: \(CNPostalAddressFormatter().string(from: package.recipient.postalAddress))
	Contents: \(contents)
	"""
	}

	func addRandomItem() {
	let weight = Int.random(in: 200…300)
	let item = PackageContent(title: "Light bulb", weight: weight)
	package.contents.append(item)
	}
	}
	}

view raw ViewModel.swift hosted with ❤ by GitHub

View model implementation for the view.

Summary

Key-value observing is getting less and less used after the introduction of Combine and SwiftUI. But there are still times when we need to connect good old KVO compatible NSObject subclasses with a SwiftUI view. Therefore, it is good to know how to handle KVO in SwiftUI views as well.

If this was helpful, please let me know on Mastodon@toomasvahter or Twitter @toomasvahter. Feel free to subscribe to RSS feed. Thank you for reading.

Project

SwiftUIMVVMKVOObserving (GitHub, Xcode 12.1)

Support me on Patreon

Donate with Paypal

Buy me a coffee

Tags @Published, @StateObject, Combine, KeyValueObservingPublisher, KVO, MVVM, objectWillChange, ObservableObject, publisher, SwiftUI

Combine CoreData Foundation Generics iOS Swift SwiftUI Xcode

Using CoreData with SwiftUI

Post author By Toomas Vahter
Post date January 19, 2020
1 Comment on Using CoreData with SwiftUI

CoreData is Apple’s object graph and persistence framework. It provides data sources for synchronising data with view. Let’s take a look on how to use those data sources in SwiftUI views. Starting with NSFetchedResultsController what is used for list and collection views, after that observing NSManagedObject directly from SwiftUI view and lastly subscribing to managed object context notifications.

NSFetchedResultsController

NSFetchedResultsController is used for providing data in table and collection views. It supports sorting and filtering data and arranging data into sections. We can use delegate for getting change callbacks. NSFetchedResultsControllerDelegate contains several methods:

	// Diffable data source (new in iOS 13)
	optional func controller(_ controller: NSFetchedResultsController<NSFetchRequestResult>, didChangeContentWith snapshot: NSDiffableDataSourceSnapshot)
	optional func controller(_ controller: NSFetchedResultsController<NSFetchRequestResult>, didChangeContentWith diff: CollectionDifference<NSManagedObjectID>)

	// Manually updating table view and collection view
	optional func controller(_ controller: NSFetchedResultsController<NSFetchRequestResult>, didChange anObject: Any, at indexPath: IndexPath?, for type: NSFetchedResultsChangeType, newIndexPath: IndexPath?)
	optional func controller(_ controller: NSFetchedResultsController<NSFetchRequestResult>, didChange sectionInfo: NSFetchedResultsSectionInfo, atSectionIndex sectionIndex: Int, for type: NSFetchedResultsChangeType)
	optional func controllerWillChangeContent(_ controller: NSFetchedResultsController<NSFetchRequestResult>)
	optional func controllerDidChangeContent(_ controller: NSFetchedResultsController<NSFetchRequestResult>)

view raw DataSources.swift hosted with ❤ by GitHub

In SwiftUI we are not going to directly manipulate views. Only what we need to do is letting SwiftUI view know that data is about to change. Let’s take a look on simple app with list of items stored by CoreData. Data is represented by ColorItem where only stored value is hex string of the color (e.g. #AA22BB).

	final class ColorItem: NSManagedObject {
	@NSManaged var hex: String
	}

view raw ColorItem.swift hosted with ❤ by GitHub

ColorItems are managed by ContentView’s view model. View model creates NSFetchedResultsController, performs fetch and provides array of fetched ColorItems to the SwiftUI’s List. In addition, view model is delegate of the NSFetchedResultsController (requires view model to be NSObject subclass). As view model is ObservableObject, we can very easily let SwiftUI view know that it should refresh. We need to do two things: firstly, implementing controllerWillChangeContent delegate method and calling send() on objectWillChange publisher. Secondly, view model property must use @ObservedObject property wrapper in SwiftUI view. Result is that SwiftUI view subscribes to objectWillChange publisher and refreshes whenever publisher emits an event.

	extension ContentView {
	final class ViewModel: NSObject, NSFetchedResultsControllerDelegate, ObservableObject {
	private let colorController: NSFetchedResultsController<ColorItem>

	init(managedObjectContext: NSManagedObjectContext) {
	let sortDescriptors = [NSSortDescriptor(keyPath: \ColorItem.hex, ascending: true)]
	colorController = ColorItem.resultsController(context: managedObjectContext, sortDescriptors: sortDescriptors)
	super.init()
	colorController.delegate = self
	try? colorController.performFetch()
	}

	func controllerWillChangeContent(_ controller: NSFetchedResultsController<NSFetchRequestResult>) {
	objectWillChange.send()
	}

	var colors: [ColorItem] {
	return colorController.fetchedObjects ?? []
	}
	}
	}

	extension ColorItem {
	static func resultsController(context: NSManagedObjectContext, sortDescriptors: [NSSortDescriptor] = []) -> NSFetchedResultsController<ColorItem> {
	let request = NSFetchRequest<ColorItem>(entityName: "ColorItem")
	request.sortDescriptors = sortDescriptors.isEmpty ? nil : sortDescriptors
	return NSFetchedResultsController(fetchRequest: request, managedObjectContext: context, sectionNameKeyPath: nil, cacheName: nil)
	}
	}

view raw ViewModelFetchedResults.swift hosted with ❤ by GitHub

And finally let’s see the ContentView implementation. NSManagedObject has objectID property what we can use in List for identifying every ColorItem. Cell is custom view what we’ll take a look at next.

	struct ContentView: View {
	@ObservedObject var viewModel: ViewModel

	var body: some View {
	NavigationView {
	VStack {
	List(viewModel.colors, id: \.objectID) { (colorItem) in
	Cell(colorItem: colorItem)
	}
	}.navigationBarTitle("Colors")
	}
	}
	}

view raw ContentViewFetchedResults.swift hosted with ❤ by GitHub

NSManagedObject

NSManagedObject implements ObservableObject protocol and therefore it is possible to use it together with @ObservedObject property wrapper and getting SwiftUI view refreshed automatically when any of the ColorItem properties change. NSFetchedResultsController required a little bit of code for setting up delegate but that is not the case with NSManagedObject.

	struct Cell: View {
	@ObservedObject var colorItem: ColorItem

	var body: some View {
	HStack {
	Text(verbatim: colorItem.hex)
	Spacer()
	Rectangle().foregroundColor(Color(colorItem.uiColor)).frame(minWidth: 50, maxWidth: 50)
	}
	}
	}

view raw Cell.swift hosted with ❤ by GitHub

In addition, if there are cases where we would like to observe specific property, then Combine provides publisher for key path. Because NSManagedObject supports key-value observing we can use the publisher and subscribe to individual property changes.

	let cancellable = color.publisher(for: \.hex).sink { (string) in
	print(string)
	}

view raw KVOPublisherSink.swift hosted with ❤ by GitHub

Subscribing to CoreData notifications

When we need to observe changes in persistent store we can observe notifications sent by the framework. As NotificationCenter supports publishers, we can subscribe to it, unpack data from notification and do something with the data. For making this easier we can introduce a separate type. It will unpack the user info dictionary and filter by type. This allows to easily observe, for example, ColorItem insertions. Or, if we would like to receive every possible change, we can specify NSManagedObject as the generic type.

	private var cancellables = [AnyCancellable]()

	let cancellable = NotificationCenter.default.publisher(for: .NSManagedObjectContextObjectsDidChange, object: managedObjectContext)
	.compactMap({ ManagedObjectContextChanges<ColorItem>(notification: $0) }).sink { (changes) in
	print(changes)
	}
	cancellables.append(cancellable)

	struct ManagedObjectContextChanges<T: NSManagedObject> {
	let inserted: Set<T>
	let deleted: Set<T>
	let updated: Set<T>

	init?(notification: Notification) {
	let unpack: (String) -> Set<T> = { key in
	let managedObjects = (notification.userInfo?[key] as? Set<NSManagedObject>) ?? []
	return Set(managedObjects.compactMap({ $0 as? T }))
	}
	deleted = unpack(NSDeletedObjectsKey)
	inserted = unpack(NSInsertedObjectsKey)
	updated = unpack(NSUpdatedObjectsKey).union(unpack(NSRefreshedObjectsKey))
	if deleted.isEmpty, inserted.isEmpty, updated.isEmpty {
	return nil
	}
	}
	}

view raw ManagedObjectContextChanges.swift hosted with ❤ by GitHub

Summary

We took a look at how to use NSFetchedResultsController and NSManagedObject in SwiftUI views. We saw that integrating NSFetchedResultsController requires only a little bit of code and using NSManagedObject even less. In addition, we looked at subscribing to CoreData notifications and unpacking notification payload.

If this was helpful, please let me know on Mastodon@toomasvahter or Twitter @toomasvahter. Feel free to subscribe to RSS feed. Thank you for reading.

Example project

CoreDataCombineSwiftUI (Xcode 11.3)

Support me on Patreon

Donate with Paypal

Buy me a coffee

Tags AnyCancellable, CoreData, List, NSDeletedObjectsKey, NSFetchedResultsController, NSInsertedObjectsKey, NSManagedObject, NSManagedObjectContext, NSObject, NSRefreshedObjectsKey, NSUpdatedObjectsKey, objectWillChange, ObservableObject, ObservedObject, persistence, persistent, SwiftUI

Combine Foundation iOS Swift SwiftUI

MVVM in SwiftUI

Let’s build a simple app using MVVM (model-view-view model) where every SwiftUI view has its own view model. It’s going to be an app with two views: list of movies and add a movie view what utilises Form view. Added movies are stored in MovieStore which is shared by the two view models. We will use environment for sharing the MovieStore. It will be read from the environment when we need to create AddMovieView with its view model.

Movie and MovieStore representing data

Movie is a small struct and just stores the title and rating. Title and rating are mutable as we are going to update those in AddMovieView. We also conform to protocol Identifiable because we are going to use List view for showing all the movies. List needs a way of identifiyng the content and its the simplest way of satisfiying the requirement.

struct Movie: Equatable, Identifiable {
    let id = UUID()
    var fullTitle: String
    var givenRating: Rating = .notSeen
}

extension Movie {
    enum Rating: Int, CaseIterable {
        case notSeen, terrible, poor, decent, good, excellent
    }
}

MovieStore is also a pretty simple although in a more sophisticated app it would contain much more logic: persistence, deleting etc. We use Published property wrapper which automatically provides a publisher we can use to subscribe against.

final class MovieStore {
    @Published private(set) var allMovies = [Movie]()
    
    func add(_ movie: Movie) {
        allMovies.append(movie)
    }
}

For inserting shared MovieStore to environment, we’ll use custom EnvironmentKey. Custom key is just an object conforming to EnvironmentKey protocol. We need to provide the type and default value.

struct MovieStoreKey: EnvironmentKey {
    typealias Value = MovieStore
    static var defaultValue = MovieStore()
}

extension EnvironmentValues {
    var movieStore: MovieStore {
        get {
            return self[MovieStoreKey]
        }
        set {
            self[MovieStoreKey] = newValue
        }
    }
}

If we do not insert our own instance of MovieStore to the environment, the instance returned by defaultValue is used. Typically we would like to use a specific instance initialised outside of the view hierarchy. Therefore let’s take a look how to do that next.

SceneDelegate and MovieScene presentation

MovieStore dependency is passed into view models with initialiser. We’ll use the instance stored in SceneDelegate. Yet again, in a real app, it would probably live in a separate dependency container or in something similar. MovieListView is the first view we need to present, therefore we’ll initialise view model, view and insert instance of MovieStore to environment for later use (movieStore keypath is the one we just defined in EnvironmentValues‘ extension).

final class SceneDelegate: UIResponder, UIWindowSceneDelegate {
    var window: UIWindow?
    private let movieStore = MovieStore()

    func scene(_ scene: UIScene, willConnectTo session: UISceneSession, options connectionOptions: UIScene.ConnectionOptions) {
        let viewModel = MovieListView.ViewModel(movieStore: movieStore)
        let contentView = MovieListView(viewModel: viewModel).environment(\.movieStore, movieStore)
        
        guard let windowScene = scene as? UIWindowScene else { return }
        let window = UIWindow(windowScene: windowScene)
        window.rootViewController = UIHostingController(rootView: contentView)
        self.window = window
        window.makeKeyAndVisible()
    }
}

MovieListView and its ViewModel

We still haven’t taken a look on MovieListView and its view model, let’s do it now. View model conforms to protocol ObservableObject and uses @Published property wrappers. ObservableObject’s default implementation provides objectWillChange publisher. @Published property wrapper automatically fires the publisher when the property value is about to change. On MovieListView we have declared view model property with @ObservedObject property wrapper. This will make the view to subscribe to objectWillChange publisher and will refresh the view when-ever objectWillChange fires.

extension MovieListView {
    final class ViewModel: ObservableObject {
        private let movieStore: MovieStore
        private var cancellables = [AnyCancellable]()
        
        init(movieStore: MovieStore) {
            self.movieStore = movieStore
            cancellables.append(movieStore.$allMovies.assign(to: \.movies, on: self))
        }
        
        @Published private(set) var movies = [Movie]()
        @Published var isPresentingAddMovie = false
    }
}

struct MovieListView: View {
    @Environment(\.self) var environment
    @ObservedObject var viewModel: ViewModel
    
    var body: some View {
        NavigationView {
            List(self.viewModel.movies) { movie in
                Text(movie.fullTitle)
            }.navigationBarTitle("Movies")
                .navigationBarItems(trailing: navigationBarTrailingItem)
        }
    }
    
    private var navigationBarTrailingItem: some View {
        Button(action: {
            self.viewModel.isPresentingAddMovie = true
        }, label: {
            Image(systemName: "plus").frame(minWidth: 32, minHeight: 32)
        }).sheet(isPresented: self.$viewModel.isPresentingAddMovie) {
            self.makeAddMovieView()
        }
    }
    
    private func makeAddMovieView() -> AddMovieView {
        let movieStore = environment[MovieStoreKey]
        let viewModel = AddMovieView.ViewModel(movieStore: movieStore)
        return AddMovieView(viewModel: viewModel)
    }
}

Changes in MovieStore are observed by subscribing to allMovies subscriber and then assigning the new list of movies to view model’s own property. Note that assignment is triggered on subscribing and when changes happen: like KVO with initial option. Only downside is that now the list is duplicated but that’s OK. We would need to do that anyway when we would like to sort or filter the list later on.

AddMovieView and its view model are created when user taps on the plus button in the navigation bar. Environment property wrapper can be used to get the whole environment or any of the values using a specific key. In current case I went for accessing the whole environment object and then getting MovieStore using a MovieStoreKey later when needed. Then the MovieStore is not available in the whole view scope and only when creating the AddMovieView. Other option would be to use @Environment(\.movieStore) var movieStore instead.

AddMovieView and its ViewModel

AddMovieView’s view model is initialised with MovieStore and internally it represents and instance of Movie. Published property wrapper is used similarly like in MovieListView’s view model. The model object is a private property and instead of direct access, two bindings are provded for TextField and Picker. Binding represents a two way connection between the view and model. In addition, there is canSave property what is used for enabling the save button in the navigation bar. Save button should be enabled only when title is filled. To recap the view update flow: TextField or Picker will use Binding to update private property newMovie. As newMovie property uses @Published property wrapper, it will fire ObservableObject’s objectWillChange publisher. SwiftUI automatically subscribes to objectWillChange because view model’s property uses @ObservedObject.

extension AddMovieView {
    class ViewModel: ObservableObject {
        private let movieStore: MovieStore
        
        init(movieStore: MovieStore) {
            self.movieStore = movieStore
        }
        
        @Published private var newMovie = Movie(fullTitle: "")
        
        lazy var title = Binding<String>(get: {
            self.newMovie.fullTitle
        }, set: {
            self.newMovie.fullTitle = $0
        })
        
        lazy var rating = Binding<Movie.Rating>(get: {
            self.newMovie.givenRating
        }, set: {
            self.newMovie.givenRating = $0
        })
        
        var canSave: Bool {
            return !newMovie.fullTitle.isEmpty
        }
        
        func save() {
            movieStore.add(newMovie)
        }
    }
}

struct AddMovieView: View {
    @Environment(\.presentationMode) private var presentationMode
    @ObservedObject var viewModel: ViewModel
    
    var body: some View {
        NavigationView {
            Form {
                titleSection
                ratingSection
            }.navigationBarTitle("Add Movie", displayMode: .inline)
                .navigationBarItems(leading: leadingBarItem, trailing: trailingBarItem)
                .navigationViewStyle(StackNavigationViewStyle())
            
        }
    }
    
    private var titleSection: some View {
        Section() {
            TextField("Title", text: viewModel.title)
        }
    }

    private var ratingSection: some View {
        Section() {
            Picker(LocalizedStringKey("Rating"), selection: viewModel.rating) {
                ForEach(Movie.Rating.allCases, id: \.rawValue) {
                    Text($0.localizedName).tag($0)
                }
            }
        }
    }
    
    private var leadingBarItem: some View {
        Button(action: { self.presentationMode.wrappedValue.dismiss() }, label: {
            Text("Cancel")
        })
    }
    
    private var trailingBarItem: some View {
        Button(action: {
            self.viewModel.save()
            self.presentationMode.wrappedValue.dismiss()
        }, label: {
            Text("Save").disabled(!self.viewModel.canSave)
        })
    }
}

Summary

We created a simple app with two views. Both views had its own view model and both view models used the same dependency: MovieStore. One view model triggered changes in MovieStore and those changes were observed by the other view model. In addition, we looked into how to use SwiftUI’s environment and how to trigger view updates from view models.

If this was helpful, please let me know on Mastodon@toomasvahter or Twitter @toomasvahter. Feel free to subscribe to RSS feed. Thank you for reading.

Example

SwiftUICombineMVVMExample (GitHub, Xcode 11.3, Swift 5)

Support me on Patreon

Donate with Paypal

Buy me a coffee

Tags Binding, Combine, Identifiable, List, model, MVVM, ObservableObject, ObservedObject, Picker, publisher, SwiftUI, View, view model

Combine iOS Swift SwiftUI

Animating view transitions in SwiftUI

Post author By Toomas Vahter
Post date December 8, 2019
2 Comments on Animating view transitions in SwiftUI

One building block for navigating from one view to another is NavigationView which is a representation of UINavigationController in UIKit. This time, let’s take a look on how to transition from one SwiftUI view to another one without NavigationView.

AppFlowCoordinator managing choosing the view

The idea is to have a root SwiftUI view with only responsibility of presenting the active view. State is stored in AppFlowCoordinator which can be accessed from other views and therefore other views can trigger navigation. Example case we’ll build, is animating transitions from login view to main view and back. As said, AppFlowCoordinator stores the information about which view should be on-screen at a given moment. All the views are represented with an enum and based on the value in enum, views are created. This coordinator is ObservableObject what makes it easy to bind to a SwiftUI view – whenever activeFlow changes, SwiftUI view is updated. The term flow is used because views can consist of stack of other views and therefore creating a flow of views.

	import SwiftUI

	final class AppFlowCoordinator: ObservableObject {
	@Published var activeFlow: Flow = .login

	func showLoginView() {
	withAnimation {
	activeFlow = .login
	}
	}

	func showMainView() {
	withAnimation {
	activeFlow = .main
	}
	}
	}

	extension AppFlowCoordinator {
	enum Flow {
	case login, main
	}
	}

view raw AppFlowCoordinator.swift hosted with ❤ by GitHub

Triggering navigation using flow controller.

RootView displaying active flow

RootView selects which view is currently visible. It accesses coordinator through environment. SwiftUI requires EnvironmentObjects to be ObservableObjects, therefore this view is automatically refreshed when activeFlow changes in the AppFlowCoordinator. RootView’s body is annotated with @ViewBuilder which will enable the view to return a body with type depending on the current state (HStack is also a ViewBuilder). Other options are wrapping the views with AnyView or using Group. In our case the view types are LoginView and ContentView. Both views also define the transition animation what is used when view refresh is triggered in withAnimation closure in AppFlowCoordinator. Asymmetric enables defining different transitions when view is added and removed from the view hierarchy.

	let appFlowCoordinator = AppFlowCoordinator()
	let rootView = RootView().environmentObject(appFlowCoordinator)
	window.rootViewController = UIHostingController(rootView: rootView)

view raw SceneDelegate.swift hosted with ❤ by GitHub

Inserting AppFlowCoordinator to environment

	struct RootView: View {
	@EnvironmentObject var appFlowCoordinator: AppFlowCoordinator

	@ViewBuilder
	var body: some View {
	ZStack {
	Color.black.edgesIgnoringSafeArea(.all)
	if appFlowCoordinator.activeFlow == .main {
	ContentView().transition(.asymmetric(insertion: .scale, removal: .opacity))
	}
	else if appFlowCoordinator.activeFlow == .login {
	LoginView().transition(.asymmetric(insertion: .slide, removal: .opacity))
	}
	else {
	EmptyView()
	}
	}
	}
	}

view raw RootView.swift hosted with ❤ by GitHub

Updating currently visible flow with transition animations

Triggering navigation from SwiftUI view

Last piece we need to take a look at is how to trigger transition. As AppFlowCoordinator is in environment, any view can access the coordinator and call any of the navigation methods. When login finishes, LoginView can tell the coordinator to show the main content view.

	struct LoginView: View {
	@EnvironmentObject var appFlowCoordinator: AppFlowCoordinator

	var body: some View {
	ZStack {
	Button(action: appFlowCoordinator.showMainView) {
	Text("Login")
	}
	}
	}
	}

view raw LoginView.swift hosted with ❤ by GitHub

Navigating to main view from login view

Summary

We took a look on how to navigate from one SwiftUI view to another by using a coordinator object. Coordinator stored the information about which view we should currently display on screen. We saw how easy it is to trigger navigation from any of the currently visible views.

Low FPS GIF representing the transition animation

If this was helpful, please let me know on Mastodon@toomasvahter or Twitter @toomasvahter. Feel free to subscribe to RSS feed. Thank you for reading.

Example

RootViewTransitions Xcode 11.2.1, Swift 5.1

Tags animation, coordinator, Environment, EnvironmentObject, flow, navigation, ObservableObject, opacity, slide, SwiftUI, transition, ViewBuilder, withAnimation

Combine iOS Swift SwiftUI

Creating chat view with Combine and SwiftUI

Post author By Toomas Vahter
Post date June 23, 2019
1 Comment on Creating chat view with Combine and SwiftUI

Let’s build a conversation view which shows a list of messages and has input text field with send button. Sent and received messages are managed by Conversation object. Conversation object manages a Session object which is simulating networking stack. This kind of setup allows us to look into how to propagate received messages from Session object to Conversation and then to the list view. We’ll jump into using types Combine and SwiftUI provide therefore if you need more information, definitely watch WWDC videos about Combine and SwiftUI.

Data layer

In the UI we are going to show a list of messages, therefore let’s define a struct for a Message. We’ll make the Message to conform to protocol defined in SwiftUI – Identifiable. We can add conformance by adding id property with type UUID what provides us unique identifier whenever we create a message. Identification is used by SwiftUI to identify messages and finding changes in the messages list.

	struct Message: Identifiable {
	let id = UUID()
	let sender: String
	let text: String
	}

view raw .swift hosted with ❤ by GitHub

Session is owned by Conversation and simulates a networking stack dealing with sending and receiving messages. This like a place were we could use delegate pattern for forwarding received messages back to the Conversation. Instead of delegation pattern, we can use Combine’s PassthroughSubject. It enables us to publish new messages which we can then collect on the Conversation side. Great, but let’s see how to receive messages which are published by PassthroughSubject.

	struct Session {
	let messageFeed = PassthroughSubject<Message, Never>()

	func send(_ message: Message) {
	DispatchQueue.main.asyncAfter(deadline: .now() + .milliseconds(100)) {
	self.messageFeed.send(message)
	self.simulateReceivingMessages()
	}
	}

	private func simulateReceivingMessages() {
	DispatchQueue.main.asyncAfter(deadline: .now() + .milliseconds(200)) {
	let receivedMessage = Message(sender: "Person B", text: UUID().uuidString)
	self.messageFeed.send(receivedMessage)
	}
	}
	}

view raw .swift hosted with ❤ by GitHub

Conversation is responsible of receiving messages from the Session and keeping the current history: list of messages. For receiving messages published by Session, we can use a subscriber called sink, which just gives access to values flowing through the channel. Subscribers are added directly to publishers, then publisher sends a subscription object back to the subscriber what subscriber can use for communicating with publisher. Here, communicating means requesting values from publisher. To recap: Session owns PassthroughSubject what Conversation starts to listen by attaching subscriber to it.

Conversation conforms to SwiftUI’s ObservableObject. When marking properties with @Published property wrapper, changes in those properties trigger updates in SwiftUI.

	final class Conversation: ObservableObject {
	private let session = Session()
	private var messageSubscriber: AnyCancellable?

	init() {
	messageSubscriber = session.messageFeed.sink { [weak self] (receivedMessage) in
	self?.messages.append(receivedMessage)
	}
	}

	@Published private(set) var messages = [Message]()

	func send(_ message: Message) {
	session.send(message)
	}
	}

view raw .swift hosted with ❤ by GitHub

Creating simple list view

In SwiftUI, views are described by value types conforming to View protocol. Every view return their content in the body property. Our UI is simple enough and requires to add navigation view, list and then input view. List is the table view construct which creates new rows whenever it needs to. As we made Message to conform to Identifiable, then we can pass the messages directly to the List.

	struct ContentView: View {
	@ObjectBinding var conversation: Conversation

	var body: some View {
	NavigationView {
	VStack {
	List(self.conversation.messages) { message in
	Text(message.text)
	}
	InputView(conversation: self.conversation)
	}.navigationBarTitle(Text("Conversation"))
	}
	}
	}

view raw .swift hosted with ❤ by GitHub

Input view contains text field and button for sending the entered message. Input text is local state owned by the view itself. @State is a property wrapper and internally it creates a separate storage where the input text is stored and read during view updates.

	import Combine
	import SwiftUI

	struct InputView: View {
	let conversation: Conversation
	@State private var inputText = ""

	var body: some View {
	HStack {
	TextField("", text: $inputText)
	.padding(6)
	.background(Color.white)
	Button(action: sendMessage) {
	Text("Send")
	}
	}.padding(12).background(Color.init(white: 0.75))
	}

	private func sendMessage() {
	self.conversation.send(Message(sender: "PersonA", text: self.inputText))
	self.inputText = ""
	}
	}

view raw .swift hosted with ❤ by GitHub

Now we have a the whole picture put together. Conversation object manages messages and lets SwiftUI know when it changes by using @Published property wrapper. When property wrapper dispatches change to SwiftUI, it compares the changes in the view hierarchy and updates only what is needed.

Summary

We created a basic list view what displays messages in the conversation object. We used simple constructs for passing on the data down from the Session to the SwiftUI layer. The aim of the sample project was to try out some of the ways Combine and SwiftUI allow us to build views.

If this was helpful, please let me know on Mastodon@toomasvahter or Twitter @toomasvahter. Feel free to subscribe to RSS feed. Thank you for reading.

Example

ConversationInSwiftUI (Xcode 11, Swift 5.1)

Resources

Data Flow Through SwiftUI (WWDC’19)
Introducing Combine (WWDC’19)
Introducing SwiftUI: Building Your First App (WWDC’19)
SwiftUI Essentials (WWDC’19)

Tags @Published, BindableObject, Combine, Conversation, didChange, ObservableObject, ObservedObject, PassthroughSubject, publisher, Sink, subscriber, subscription, SwiftUI, View