Question 1

How does the route stack work in Navigator?

Accepted Answer

Navigator keeps a stack of routes; push adds a screen, and pop removes the current one and returns to what is beneath it.

Question 2

What are the clear ways to pass data between routes?

Accepted Answer

Pass required constructor arguments to the new page, and return a result from pop when the previous screen needs a value.

Question 3

What should happen when a deep link is opened directly?

Accepted Answer

The app converts the URL into an understandable route state, checks permissions and data, and then builds a suitable stack instead of assuming the user started from home.

Question 4

When do you choose imperative navigation and when declarative navigation?

Accepted Answer

Imperative suits a quick local navigation command, while declarative describes the stack from state and is preferred when links, auth, or deep links change constantly.

Question 5

How do you design nested navigation for tabs or an independent flow?

Accepted Answer

Give each flow a clear Navigator or route scope, and define which back action belongs to the child and which exits to the parent.

Question 6

How do you use go_router for declarative navigation, route guarding (redirect), and deep links?

Accepted Answer

go_router defines a tree of routes by URL, turns the link into a stack of screens, and offers a central redirect that decides where the user goes based on sign-in state, with support for deep links and the web.