Top-notch video tutorials for Swift developers

This time we'll focus on moving on from a simple string to a data structure that can capture the status of each guessed letter.

In this episode we will handle the enter key and migrate our state to contain an array of guesses. We will then refactor to an observable object to better encapsulate state changes and to enable testability.

Let's make the letters bounce a little as they are being typed. To do this we'll have to see how animated state changes are performed and how we can restructure our view hierarchy to achieve the results we're after.

In this episode we'll design a letter grid and build up text input using a hidden textfield, displaying the typed letters in our own UI.

In this episode we create an image cache using an actor that provides disk-caching for images from the Unsplash API. We'll also talk about Sendable and enable some compiler warnings to help us catch potential issues.

In this episode we will look at two ways of generating async values with AsyncStream. We'll examine the difference between the push and pull models and how to deal with back pressure.

We explore how we might encapsulate logic within an AsyncSequence and introduce the need for a type erased version. Type-erasure has some pros and cons and in this video we will explore how to create one called AnyAsyncSequence and how we can use it.

In this episode we will see how to create and use our own AsyncSequence, which allow us to iterate over values that can arrive asynchronously. We'll see how this compares to traditional sequences and how to make use of AsyncIterator to build our own AsyncSequence implementations.

The unit of work in Swift Concurrency is the Task. In this episode we will see how tasks are created and structured, how to run work in parallel, and how to handle cancellation by aborting work or returning partial results.

Actors are a new first class concept in swift. In this episode we will explore the problem they solve and how to use them to avoid race conditions which can lead to inconsistent results or even crashes.

Continuations are great for adapting completion-handler APIs to the new async await world. But what about delegate callbacks, which happen in an entirely separate method? In this episode we will adapt 2 delegate APIs into async await to see how this works.

With Continuations we can bridge the non-async world and make it async. Continuations allow us to take the result of a completion block and turn it into an async flow. In this episode we will see the difference between checked and unchecked continuations as well as their throwing variants.

In this episode we will see how URLSession can be used with async await. With this new API you can easily send network request and await a tuple of both the data and the response object.

In this episode we will see how we can run tasks concurrently with concurrent for loops, which is useful when the number of items you want to process is dynamic. With Task Groups you can process results asynchronously and assemble the results in a safe way.

In this episode we will show how the async await keyword can simplify asynchronous code, reading top-down as if it were synchronous, but without blocking any threads. We'll also see how async let can allow you to process multiple values concurrently.

If you're using CocoaPods already, then mixing with Swift Packages can prove to be infeasible. You can create your modules as internal pods as well, however there are a few gotchas. In this episode I will cover how to do this, how to link up local pods and create example projects for demo UI and running tests, as well as how to overcome some of the rough edges you might experience.

Now that we've seen how to setup a feature module, we'll also need to decide how best to share a feature's resources and deal with dependencies.

One big benefit of modularizing an application is working on features as modules. Let's re-create the welcome screen experience as a feature module using Swift Package Manager and Xcodegen.

In this episode we create a modularized setup where our modules are Swift Packages and brought into the main app using Xcodegen and local path references to the packages.

One thing that can be a pain when splitting modules up into separate projects is maintaining the Xcode projects themselves. Not to mention the fact that as team sizes grow, merging changes in project files gets exponentially more painful. In this episode we will look at using Xcodegen to have a repeatable project generation that you can use to create consistent Xcode projects without much fuss.

Breaking your code into discrete modules will surface a problem if your code is tightly interconnected. Once you've defined your module boundaries you now are forced to not cause bidirectional dependencies. In this episode we will look at some strategies for breaking apart dependencies into abstractions first using protocols, then using protocol witnesses. We can then depend on those abstractions in our isolated module projects.

One way of achieving modularization is to build frameworks using nested Xcode projects. This has the benefit of having everything in one place and can easily build the entire thing. You can also zero-in on a single project and just work from there if you want. Each sub-project can have its own tests, sample application, etc.

In this episode we will talk about the overview and motivation for a modular project architecture. Why split things up? I'll talk about the problems we face, what benefits we may achieve, and how can we approach the problem.

Pluralization rules vary by language, so it's not as easy as just adding an "s". To properly handle these cases, we need to use a Stringsdict file and format our string using a special syntax.