Cassius Pacheco hi cassius, this is great and thank you very much for the quick response. it is funny that right after sending this message I also came up with a similar solution. although in my case I opted in to having each view model to define its own possible routes, so that it doesn’t have the full power of accessing anywhere in the app. so it emits events from the view model (such as emitting second event to the navigationEvents publish subject) which gets observed in the view state and then view state does the navigation. i liked the fact that you abstracted the observation part and put that to the base class. also liked the AppRouteAction enum you defined to even further abstract the routing. great job for one of the most complete and clean flutter architecture post.

hey cassius, this is a great post. really appreciate it. i am pretty new to flutter and have one question. how would you navigate to another screen after a post api call here? say the view state is updated after a login and now i can navigate to home screen. since i expect that to be communicated via state update. the only place appear to me to do this is just above where you return the Scaffold but that doesn't feel right, since it would be updating the view.