@Thomas Nattestad Not sure how well aware you are with NavHost containers. Like single screen entry point and replace compose subparts. Not sure if web Canvas can do that, but would assume similar solution as iOS working. As web more url based navigation not sure how that would work in WASM world. Basically all platforms need a unified way of dealing with navigation, including dialogs and such. Very complex.
If have any ideas how solve this cross compose platform on web very curious hear your thoughts. Architecture wise bridge ui and domain layers with stuff such as screen transitions and nested navigation stacks. In theory I guess compose could handle it alone but would still require compose multiplatform supports it or libraries compatible with these concepts.
Its the only layer I feel is not solved nice in any platform. Like dependency injection, nested navigation graphs, conditional navigation (auth) and such.