Navigator.push() vs Navigator.pushNamed() when passing data to screen

Question

I would like to pass data to another screen. According to the docs when using named routes I need to use Arguments and use:

Navigator.pushNamed(
  context,
  NextScreen.route,
  arguments: NextScreenArgs("pew"),
);

However the same(?) could be accomplished by just using:

Navigator.push(
  context,
  MaterialPageRoute(
    builder: (context) => NextScreen("pew"),
  ),
);

Is there any difference or advantage using pushNamed?

score 15 · Accepted Answer · answered Feb 29 '20 at 14:35

Flutter team has a discussion about routing on github. I like this explanation:

While navigation without using named routes is OK for smaller projects, in more complex apps it adds code duplication. This is especially true if you have a route guard to only allow signed-in users enter certain pages, or any other kind of logic which needs to run as the user navigates.

Also you can read more discussions here: https://github.com/flutter/flutter/issues/3867

score 4 · Answer 2 · answered Oct 06 '20 at 11:08

4

Navigator.push() method works when you have only two or three routes. But when it comes to complex apps, you might have multiple routes. In that case, if we use Navigator.push() method then it will result in a lot of code duplication.

answered Oct 06 '20 at 11:08

Hamza Farooq

49
4

1

Why a lot of code duplication? We will use pushNamed instead of push, this time there won't be pushNamed duplication? – Emirhan Selim Uzun Oct 17 '22 at 17:06

Navigator.push() vs Navigator.pushNamed() when passing data to screen

2 Answers2