Top-notch video tutorials for Swift developers

To allow the user to edit the text elements, we'll add a binding for isEditing and swap out the Text element for a TextField. We'll then utilize onSubmit and a tap gesture to go in and out of the edit mode. Finally, using a derived binding, we can ensure that only one field is showing as editable at a given time.

In this episode we will add a toolbar button to add new text elements. We'll see how to quickly add a stroke around our text to make it readable. Then we'll implement smooth dragging to position the text elements on the canvas.

We start with a literal blank canvas. We'll use NSApplicationDelegateAdaptor and NSDocumentController with our SwiftUI app to ensure a new document is always created on launch. Then we'll introduce drag & drop behavior to allow a user to drag an image from the Finder to our app to display it.

We start looking at SwiftUI on the Mac. We'll go over how document-based apps work, and see how much functionality and standard behavior we can get with just a few lines of code. This will be the basis for a new app we'll make called Memeify.

Storing secrets in plain-text in your source code is not a great idea. It can lead to leaking this information to the wrong people (or to a wider audience than is necessary), it makes rotating these keys difficult, and it makes it trivial for people to see these secrets in your compiled application binary. In this episode we will utilize an obfuscation approach that may just be good enough for many use cases.

When working on a large project with multiple developers, we often find ourselves in contention with the Xcode project.pbxproj file. Conflicts here are not easy to solve manually, and if you make a mistake Xcode won’t load the project at all, requiring you to fix it manually. In this episode we will explore migrating to a solution where the project file is generated using a tool called Xcodegen.

In this episode we fix an issue that caused our sorting logic to be lost after adding persistence.

Now that we have a working Todo app, it's time to focus on persistence, so that our changes are kept when we launch the app. This will change the structure slightly, as we'll bring in a popular new library called Boutique and its Store to provide this facility. We'll also introduce the concept of a "controller", which is more of a model controller than a controller you might be familiar with in UIKit MVC.

In this video we discuss a couple of options for implementing drag to reorder so that we can reorder our todos. We also implement a feature to automatically move completed todos to the bottom, and bringing them back when unchecked.

In this episode we'll implement swipe to delete so we can remove todo items.

In this episode we make the todos editable and implement keyboard avoidance. We create a "new todo" button and then set up programmatic control over focus. Along the way we'll see why choosing a proper Hashable value is important.

In this episode we design a checkbox for our todo UI. We see how we can stroke and fill shapes, how to use InsettableShape, and how to apply a shadow without applying it to every view in the hierarchy.

Kicking off a new series on building a Todo App in SwiftUI. In this episode we focus primarily on the preliminary data structure, deciding who owns this data and when to use State versus Bindings when separating our app into distinct views.

Bindings are a core concept in SwiftUI. We can easily convert a @State property wrapper to a binding of its value, and we can traverse keypaths to get Bindings of nested values. What if we wanted to transform the values, or update values inside of collections? In this episode we will explore creating map for transforming bindings, unwrap for transforming optional bindings, and take a look at how bindings with collections work under the hood.

Property Wrappers are great for encapsulating cross-cutting concerns and simplifying common patterns. However, previously it seemed impossible to access the enclosing instance to enable more advanced and useful behaviors. As it turns out, this was supported all along, just in a not-so-obvious way. Let me show you.

Sometimes we run into issues where SwiftUI doesn't quite do what we need. In some cases, SwiftUI views are powered by UIKit under the hood. Wouldn't it be great (and devious) to dig into the underlying UIKit views to customize things when vanilla SwiftUI just won't cut it? In this episode we'll look at a technique for discovering the UIKit underneath SwiftUI views.

In this episode we will examine FocusedValue and FocusedBinding, which are property wrappers that allow you to react to some state when a nearby field gets focused.

There are a number of types, propertyWrappers and view modifiers describing "focus" so it is not immediately obvious what they are all for. In this episode we will see how we can control focus for a text field in SwiftUI. We'll see how to use simple Bools as well as your own types to describe which field has focus. Finally we'll touch on a common request that doesn't yet have a great answer: setting focus in onAppear.

In iOS 15 we can take advantage of the long-awaited OSLogStore, which allows you to capture and filter logs for your process on device. In this episode we will examine the NSScreencast application, which utilizes logging pretty extensively. We will build a rudimentary debug shake menu to show recent logs.

iOS 14 brought some nice improvements to os_log via a new type called Logger. This leverages Swift's StringInterpolation type to make it much more usable for formatting values inside your logs. It does this without sacrificing the privacy and performance that makes os_log so appealing. In this episode we will see how we can adopt this new API as well as how StringInterpolation works under the hood.

One of the most impactful things you can do to improve productivity is to improve turnaround time when iterating on features. Playgrounds and Xcode Live Previews are great, but both have their limitations. In this episode we will explore how to utilize hot module reloading to have the simulator automatically reflect your changes when you save. It's magic, and will blow your mind!

We now have all the pieces in place to make this game playable. We'll choose a random word, and then move on to detecting won/lost games and provide the ability to restart and keep playing.

In this episode we create a custom transition using a GeometryEffect to add a nice flip animation for the letters as they are revealed.

Now that we have some information associated with each of our typed characters, we can use that to color each letter according to its status.