Nested navigation in Flutter - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to create a nested Navigator widget.

Flutter

Navigator(
  key: [1],
  onGenerateRoute: (settings) {
    return MaterialPageRoute(builder: (context) => HomeScreen());
  },
)

Drag options to blanks, or click blank then click option'

AnavigatorKey

BnestedKey

CkeyNavigator

DnavKey

Attempts:

3 left

💡 Hint

Common Mistakes

Using an undefined variable name for the key.

Omitting the key parameter.

The Navigator widget requires a key to manage its state. The common name is 'navigatorKey'.

2fill in blank

medium

Complete the code to push a new route inside the nested navigator.

Flutter

navigatorKey.currentState?.[1](MaterialPageRoute(builder: (_) => DetailScreen()));

Drag options to blanks, or click blank then click option'

Apush

Bpop

Creplace

DpopAndPushNamed

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'pop' instead of 'push' to navigate forward.

Using 'popAndPushNamed' without named routes.

To navigate to a new screen inside a Navigator, use the push method.

3fill in blank

hard

Fix the error in the nested navigator's route generation by completing the missing return statement.

Flutter

onGenerateRoute: (settings) {
  switch (settings.name) {
    case '/':
      return MaterialPageRoute(builder: (_) => HomeScreen());
    case '/details':
      return [1](builder: (_) => DetailScreen());
    default:
      return null;
  }
}

Drag options to blanks, or click blank then click option'

ARoute

BCupertinoPageRoute

CMaterialPageRoute

DPageRouteBuilder

Attempts:

3 left

💡 Hint

Common Mistakes

Returning null instead of a valid route.

Using a route type incompatible with Material design.

MaterialPageRoute is the standard route type for material design apps and should be returned here.

4fill in blank

hard

Fill both blanks to define a nested Navigator with initialRoute and onGenerateRoute.

Flutter

Navigator(
  key: [1],
  initialRoute: [2],
  onGenerateRoute: (settings) {
    if (settings.name == '/') {
      return MaterialPageRoute(builder: (_) => HomeScreen());
    }
    return null;
  },
)

Drag options to blanks, or click blank then click option'

AnestedNavigatorKey

B"/home"

C"/"

DmainNavigatorKey

Attempts:

3 left

💡 Hint

Common Mistakes

Using the main navigator's key instead of a nested one.

Setting initialRoute to a non-existent route.

The nested navigator needs a unique key and the initialRoute is usually set to '/'.

5fill in blank

hard

Fill all three blanks to create a nested navigator with a GlobalKey, push a route, and pop it.

Flutter

final [1] = GlobalKey<NavigatorState>();

// Push a new screen
[1].currentState?.[2](MaterialPageRoute(builder: (_) => SettingsScreen()));

// Pop the current screen
[1].currentState?.[3]();

Drag options to blanks, or click blank then click option'

AnestedNavigatorKey

Bpush

Cpop

DnavigatorKey

Attempts:

3 left

💡 Hint

Common Mistakes

Using different variable names for the key.

Using pop to push a route or vice versa.

We define a GlobalKey named nestedNavigatorKey, use push to add a route, and pop to remove it.

Practice

1. What is the main purpose of nested navigation in a Flutter app?

easy

A. To manage navigation inside a specific part of the app separately

B. To replace the main Navigator of the app

C. To create multiple apps inside one Flutter project

D. To disable navigation on certain screens

Solution

1. Step 1: Understand nested navigation concept

   Nested navigation allows managing navigation stacks inside a part of the app independently from the main app navigation.

2. Step 2: Identify the purpose

   This helps keep navigation organized and user-friendly by isolating navigation flows.

3. Final Answer:

   To manage navigation inside a specific part of the app separately -> Option A

4. Quick Check:

   Nested navigation = Manage part navigation separately [OK]

Hint: Nested navigation isolates navigation flows inside app parts [OK]

Common Mistakes:

• Thinking nested navigation replaces the main Navigator
• Confusing nested navigation with multiple apps
• Assuming nested navigation disables navigation

2. Which Flutter widget is essential to implement nested navigation?

easy

A. MaterialApp

B. Container

C. Scaffold

D. Navigator

Solution

1. Step 1: Identify widget for navigation

   The Navigator widget manages a stack of routes and is essential for navigation in Flutter.

2. Step 2: Confirm nested navigation use

   Nested navigation uses a Navigator with a unique key inside a widget subtree.

3. Final Answer:

   Navigator -> Option D

4. Quick Check:

   Navigator widget = navigation management [OK]

Hint: Navigator widget controls navigation stacks [OK]

Common Mistakes:

• Choosing MaterialApp which is for app-wide setup
• Selecting Scaffold which is for layout
• Picking Container which is a basic layout widget

3. Given this nested Navigator code snippet, what screen will be shown first inside the nested navigator?

Navigator(
  key: _nestedKey,
  onGenerateRoute: (settings) {
    return MaterialPageRoute(
      builder: (context) => NestedHomeScreen(),
    );
  },
)

medium

A. NestedHomeScreen

B. The main app's home screen

C. An error because onGenerateRoute is missing

D. A blank screen

Solution

1. Step 1: Analyze onGenerateRoute usage

   The onGenerateRoute callback returns a MaterialPageRoute with NestedHomeScreen as the builder.

2. Step 2: Determine initial screen

   Since this is the only route generated, NestedHomeScreen will be the first screen shown inside the nested Navigator.

3. Final Answer:

   NestedHomeScreen -> Option A

4. Quick Check:

   onGenerateRoute returns NestedHomeScreen [OK]

Hint: onGenerateRoute builder shows initial nested screen [OK]

Common Mistakes:

• Confusing main app screen with nested screen
• Assuming missing route causes error
• Expecting blank screen without routes

4. What is wrong with this nested Navigator code?

Navigator(
  onGenerateRoute: (settings) {
    return MaterialPageRoute(
      builder: (context) => NestedScreen(),
    );
  },
)

It causes navigation issues inside the app.

medium

A. Not wrapping Navigator inside a Scaffold

B. Using MaterialPageRoute instead of CupertinoPageRoute

C. Missing a unique key for the nested Navigator

D. Not defining initialRoute property

Solution

1. Step 1: Check Navigator setup

   For nested navigation, Navigator should have a unique GlobalKey to manage its own stack separately.

2. Step 2: Identify missing key

   This code lacks a key, which can cause navigation conflicts or unexpected behavior.

3. Final Answer:

   Missing a unique key for the nested Navigator -> Option C

4. Quick Check:

   Nested Navigator needs unique key [OK]

Hint: Always assign a unique key to nested Navigator [OK]

Common Mistakes:

• Thinking route type causes issues
• Believing Scaffold is mandatory for Navigator
• Assuming initialRoute is required

5. You want to create a tabbed interface where each tab has its own navigation stack. Which approach correctly implements nested navigation for this use case?

hard

A. Use a single Navigator for the whole app and switch tabs by pushing routes

B. Use a Navigator with a unique key inside each tab widget to manage its own stack

C. Use multiple MaterialApp widgets, one per tab

D. Use IndexedStack without any Navigator inside tabs

Solution

1. Step 1: Understand tab navigation needs

   Each tab should maintain its own navigation stack independently to allow back navigation inside tabs.

2. Step 2: Apply nested Navigator per tab

   Using a Navigator with a unique key inside each tab widget isolates navigation stacks correctly.

3. Step 3: Evaluate other options

   Single Navigator can't isolate stacks; multiple MaterialApps is heavy and incorrect; IndexedStack alone doesn't handle navigation.

4. Final Answer:

   Use a Navigator with a unique key inside each tab widget to manage its own stack -> Option B

5. Quick Check:

   Nested Navigator per tab = isolated stacks [OK]

Hint: Assign unique Navigator per tab for independent navigation [OK]

Common Mistakes:

• Using one Navigator for all tabs causing stack conflicts
• Trying multiple MaterialApps which is not recommended
• Ignoring Navigator inside tabs and losing navigation control