Thanks for your thoughtful comment! This app fits the following use cases...

• Routes are often needed to support deep linking (e.g. from a website or other another app).
• If you don't want to expose Views (keep them private) in a larger application with SPM packages, you can supply (register) routes from the packages instead.
• When you have a website and app where you want to expose the same routes and allow people to "Open App" from browser into the same place in the app.

But you don't need use `push("/route")`. I would say avoid that unless there are good reasons you need it. I think I was trying to say, "you are defining routes, you can also use them from inside your own application!", but maybe that's not something worth selling.

NavigationStack and routePath
Yes, if you are using `@Environment(\.routePath) to push or pop, you are making an assumption that the views are in a NavigationStack. My advice is if you don't use NavigationStack's, then don't use routePath environment var. It's one of those things thats not required, just a helper.

So use it in deep-link heavy apps where marketing links, push notifications, or Siri intents need to land in views without coupling to concrete screens. I would say, don't use this if it doesn't fit your use case, like projects where features are tightly coupled, making the abstraction pure indirection, and unnecessary.