Book Image

Animating SwiftUI Applications

By : Stephen DeStefano
Book Image

Animating SwiftUI Applications

By: Stephen DeStefano

Overview of this book

Swift and SwiftUI are the backbone of Apple application development, making them a crucial skill set to learn. Animating SwiftUI Applications focuses on the creation of stunning animations, making you proficient in this declarative language and employing a minimal code approach. In this book, you'll start by exploring the fundamentals of SwiftUI and animation, before jumping into various projects that will cement these skills in practice. You will explore some simple projects, like animating circles, creating color spectrums with hueRotation, animating individual parts of an image, as well as combining multiple views together to produce dynamic creations. The book will then transition into more advanced animation projects that employ the GeometryReader, which helps align your animations across different devices, as well as creating word and color games. Finally, you will learn how to integrate the SpriteKit framework into our SwiftUI code to create scenes with wind, fire, rain, and or snow scene, along with adding physics, gravity, collisions, and particle emitters to your animations. By the end of this book, you’ll have created a number of different animation projects, and will have gained a deep understanding of SwiftUI that can be used for your own creations.
Table of Contents (18 chapters)

Animating an Elevator

Welcome to the elevator project! In this one, we’re going to create a working elevator, complete with sounds, floor lights, a button, and even some images of people inside. We will control the elevator using timers that are available from the Swift timer class, as we have done in previous projects.

To bring these elements together, we’ll create a data model using the @ObservableObject protocol. Apple recommends making a data model as the place to store and process the data that the application uses. The data model is also separate from the app’s user interface, where the views are created. The reason to keep data and the UI separate is that this paradigm fosters modularity and testability. It’s easier to find bugs in your logic when the data is not mixed in with UI code. Once we have the data model set up, we can then publish that data anywhere in the app using publishing wrappers, as we will see later.

In this chapter, we will...