Right now, I'm just trying to set the library up in the Maitsu project such that I can reliably render the views that I want. This is the getting-to-know-you phase where I'm just trying to figure out how things are supposed to be wired up. I'm not sure if the documentation is bad or if I'm just dumb, so this part is very frustrating. It's probably a little bit of both.

So far, it seems like there's three main structures to deal with: Coordinator, Action and Route. There's a lot of duplication in each, which I don't like very much.

The Coordinator handles all of the logic which represents a flow. It seems to consume both Action and Route. It uses Route to determine which view to render, and uses Action to determine what to do...? Action does things like appending routes and creating child coordinators.

There were also a few files that the tutorial in the repo's README didn't really mention that I had to make myself, and I only figured it out after reading through the example project.

Anyway, my app compiles with all of these, but the view I expect to render isn't rendering, so I need to dig more into what I'm doing wrong. It's hard because there's no tab bar example despite how common of a pattern that is, so I'm just flying off of some bullet points the maintainer wrote in an issue: https://github.com/erikdrobne/SwiftUICoordinator/issues/33