We now have some basic infrastructure in place for our sign up flow. We have a root navigation stack, and we have the ability to drill-down to the first screen of the flow. Pretty simple so far, but we did get to demo a fun new superpower of the @Reducer macro, which is that it generates all of the boilerplate necessary to model an enum of features, which is common for navigation stacks and tree-based navigation.

Let’s keep going. Let’s add the second step to the sign up flow, and this will make us come face-to-face with sharing data between features.