Navigation, Routing & Deep Links — Flutter Course

What you'll learn

Design URL-aware navigation with go_router, nested routes, redirects, deep links, state restoration, and predictable back behavior. The lesson turns the APIs into a repeatable engineering workflow instead of a collection of isolated snippets.

By the end of this lesson, you'll be able to:

Apply Navigator model in a production-shaped Flutter feature
Apply go_router in a production-shaped Flutter feature
Apply Parameters in a production-shaped Flutter feature
Apply Shell routes in a production-shaped Flutter feature

Core mental model

Connect each API to the decision it supports. Flutter code stays maintainable when state, ownership, lifecycle, and platform boundaries are explicit.

Concept	What it means	Decision rule
Route state	The URL-like description of current navigation	Make shareable destinations reconstructible from path and query data
Redirect	A routing rule that derives a new location from app state	Keep it deterministic and avoid side effects
Shell route	A persistent navigation frame around nested destinations	Use for tabs or rails whose state should survive child navigation

Professional workflow

Work in small vertical slices and keep behavior observable from the first iteration.

Define the declarative course routing boundary: user goal, inputs, visible states, ownership, and expected failures.
Build the smallest working vertical slice with typed data and explicit dependencies.
Represent loading, empty, success, and failure behavior where the feature can encounter them.
Verify logic away from the UI, then exercise the rendered behavior at its public boundary.
Inspect lifecycle, accessibility, performance, security, and platform behavior before widening the feature.
Refactor only after behavior is protected by repeatable evidence.

Protect the frame

Keep build methods predictable, move side effects to explicit owners, and measure before introducing caches, isolates, or architectural layers.

Guided Flutter lab

Build a focused declarative course routing slice

This compact example keeps the important ownership and data-flow decisions visible so the behavior is easy to extend and test.

lib/router.dart

final router = GoRouter(
  routes: [
    GoRoute(path: '/', builder: (_, __) => const CourseListScreen()),
    GoRoute(
      path: '/courses/:courseId/lessons/:lessonId',
      builder: (context, state) => LessonScreen(
        courseId: state.pathParameters['courseId']!,
        lessonId: state.pathParameters['lessonId']!,
      ),
    ),
  ],
  errorBuilder: (_, state) => NotFoundScreen(location: state.uri.toString()),
);

Production practice

Contract

Define the declarative course routing inputs, outputs, owner, lifecycle, visible states, and platform assumptions before selecting APIs or packages.

Verification

Protect pure rules with unit tests and the rendered public contract with widget or integration evidence; include one unavailable or failure case.

Operations

Keep dependencies replaceable, log actionable context without user secrets, and measure user-visible behavior before optimizing.

Common failure mode

Passing complete mutable objects as hidden route extras makes deep links, browser refresh, restoration, and process recreation unreliable.

Independent workshop

Extend the guided lab into a review-ready declarative course routing feature that fits the running course portfolio app.

Your finished workshop must include:

Navigator model
go_router
Parameters
Shell routes
Redirects
Automated verification and a short design note

Definition of done

Demonstrate the happy path, an empty or unavailable state, and at least one failure path. Add an automated check and a short note explaining one design decision.

Recap & quick check

Key takeaways

Route state: Make shareable destinations reconstructible from path and query data
Redirect: Keep it deterministic and avoid side effects
Shell route: Use for tabs or rails whose state should survive child navigation

Quick check

1. Which rule best applies to Route state?

2. Which rule best applies to Redirect?

3. Which rule best applies to Shell route?

Next: Responsive & Adaptive Design