Good news Ali, I've just posted the part 2 of the series that explains routing https://cassiuspacheco.com/flutter-mvvm-and-clean-architecture-part-2-testable-routing-ckwkjnkph0dmngns1cf8e7d5n

Hello, thanks for the feedback! About routing, you really want to keep the logic about where and how you're navigating to in the view model, so you can unit test it as well as have complex routing systems depending on user interactions, like you mentioned, after an API call, for example. Now, you don't want to access widgets, context, Navigators, etc in the view model, you only want the pure logic in there, such as the routing logic. If you want a spoiler of the next post showing how I do it, have a look at the part 2 of the series code https://github.com/CassiusPacheco/flutter_mvvm/commit/fbd7237ed1f08993becf16ff7a80ec6aacee044f The post explaining it will be coming up soon. Hope that helps!