Basic Routing with Flutter Navigator 2.0 Example
Did you know? The Flutter team launched Navigator 2.0 to manage complicated routing. It is because Navigator 1.0 was only capable of adding and deleting pages from stacks. This made it difficult to handle deep linking or URI parsing for Flutter Web. But can Navigator 2.0 really solve this problem? For that, we need to understand Flutter Navigator 2.0 in greater detail. It will also make the process of Flutter app development simpler for you in the future. Overview of Flutter Navigator! Navigator 1.0 is an imperative API. In contrast, flutter’s Navigator 2.0 operates mostly in an imperative manner. Yet, it has a declarative API. In the case of Navigator 1.0, there was a stack through which one could push or pop pages. It was pretty and convenient. But it offered these benefits until the application had simple routing. Simple Routing consisted of the use of fewer screens and used on the web. The issue became grave when users had to create complicated apps. Implementation of “deep linki