Book Image

SwiftUI Essentials – iOS 14 Edition

By : Neil Smyth
Book Image

SwiftUI Essentials – iOS 14 Edition

By: Neil Smyth

Overview of this book

Do you want to create iOS apps with SwiftUI, Xcode 12, and Swift 5.3, and want to publish it on the app store? This book helps you achieve these skills with a step-by-step approach. This course first walks you through the steps necessary to set up an iOS development environment together and introduces Swift Playgrounds to learn and experiment with Swift—specifically, the Swift 5.3 programming language. After establishing key concepts of SwiftUI and project architecture, this course provides a guided tour of Xcode in SwiftUI development mode. The book also covers the creation of custom SwiftUI views and explains how these views are combined to create user interface layouts, including the use of stacks, frames, and forms. One of the more important skills you’ll learn is how to integrate SwiftUI views into existing UIKit-based projects and explain the integration of UIKit code into SwiftUI. Finally, the book explains how to package up a completed app and upload it to the app store for publication. Along the way, the topics covered in the book are put into practice through detailed tutorials, the source code for which is also available for download. By the end of this course, you will be able to build your own apps for iOS 14 using SwiftUI and publish it on the app store. The code files for the book can be found here: https://www.ebookfrenzy.com/retail/swiftui-ios14/
Table of Contents (56 chapters)
56
Index

22.6 Summary

SwiftUI provides three ways to bind data to the user interface and logic of an app. State properties are used to store the state of the views in a user interface layout and are local to the current content view. These transient values are lost when the view goes away.

For data that is external to the user interface and is required only by a subset of the SwiftUI view structures in an app, the observable object protocol should be used. Using this approach, the class or structure which represents the data must conform to the ObservableObject protocol and any properties to which views will bind must be declared using the @Published property wrapper. To bind to an observable object property in a view declaration the property must use the @ObservedObject or @StateObject property wrapper (@StateObject being the preferred option in the majority of cases).

For data that is external to the user interface, but for which access is required for many views, the environment object...