Hi. Thx for your article. I think your pattern is good, well structured and implemented. Just missing the handling of async generation of initialRoute.

And what you missed the most about Navigator 2.0 is that its purpose is not to replace Navigator 1.0 but to fix some missing like navigation history binding. The best way to see the limitions of Navigator 1.0 is to use it in Flutter Web where you have to handle changes of Browser url from app and app changes from browser url. History and State of navigation is better handled in Navigator 2.0 and it goes deeper cause you can provide your own route Provider to handle deeplink from notification or else…