Book Image

SwiftUI Cookbook

By : Giordano Scalzo, Edgar Nzokwe
Book Image

SwiftUI Cookbook

By: Giordano Scalzo, Edgar Nzokwe

Overview of this book

SwiftUI is an innovative and simple way to build beautiful user interfaces (UIs) for all Apple platforms, right from iOS and macOS through to watchOS and tvOS, using the Swift programming language. In this recipe-based book, you’ll work with SwiftUI and explore a range of essential techniques and concepts that will help you through the development process. The recipes cover the foundations of SwiftUI as well as the new SwiftUI 2.0 features introduced in iOS 14. Other recipes will help you to make some of the new SwiftUI 2.0 components backward-compatible with iOS 13, such as the Map View or the Sign in with Apple View. The cookbook begins by explaining how to use basic SwiftUI components. Then, you’ll learn the core concepts of UI development such as Views, Controls, Lists, and ScrollViews using practical implementation in Swift. By learning drawings, built-in shapes, and adding animations and transitions, you’ll discover how to add useful features to the SwiftUI. When you’re ready, you’ll understand how to integrate SwiftUI with exciting new components in the Apple development ecosystem, such as Combine for managing events and Core Data for managing app data. Finally, you’ll write iOS, macOS, and watchOS apps while sharing the same SwiftUI codebase. By the end of this SwiftUI book, you'll have discovered a range of simple, direct solutions to common problems found in building SwiftUI apps.
Table of Contents (15 chapters)

Chapter 10: Handling Authentication and Firebase with SwiftUI

Since the creation of the mobile apps market, one of the most important features most apps utilize is authentication.

The normal way app creators ensure authentication is provided is by ensuring the user creates a new profile in the app they are using.

However, this creates some problems regarding the user-friendliness of the app. This is because before the user can use the app, they must do something that could be considered time-consuming, which means they might leave the app without using it.

There are also security concerns here. Because creating a new profile for each app we use is a repetitive process, we could be tempted to reuse a password we've already used somewhere else. For example, if a data breach occurs on any of the apps we've used and we've used the password for that app elsewhere, our other accounts that use that password are vulnerable to being hacked.

To overcome this problem...