Passing data between screens in Flutter - UI Render Trace

Component - Passing data between screens

This UI component shows how to send data from one screen to another in a Flutter app. When you tap a button on the first screen, it opens a second screen and passes a message to display.

Widget Tree

MaterialApp
└── Scaffold (HomeScreen)
    ├── AppBar
    └── Center
        └── ElevatedButton

MaterialApp
└── Scaffold (DetailScreen)
    ├── AppBar
    └── Center
        └── Text

The app starts with a MaterialApp widget. The HomeScreen uses a Scaffold with an AppBar and a centered ElevatedButton. When pressed, it navigates to DetailScreen, which also uses a Scaffold with an AppBar and a centered Text widget showing the passed message.

Render Trace - 5 Steps

Step 1: MaterialApp

Step 2: HomeScreen Scaffold

Step 3: ElevatedButton

Step 4: Navigator.push

Step 5: DetailScreen Scaffold

State Change - Re-render

Trigger:User taps the 'Go to Detail' button on HomeScreen.

Before

HomeScreen is visible with the button.

→

After

DetailScreen is visible showing the passed message.

Re-renders:The entire screen changes from HomeScreen to DetailScreen.

UI Quiz - 3 Questions

What happens when the button on the HomeScreen is tapped?

A The button changes its label.

B The app closes.

C The app navigates to DetailScreen and passes a message.

D Nothing happens.

Key Insight

Passing data between screens in Flutter is done by sending arguments when navigating. The Navigator widget manages screen transitions, and the receiving screen uses constructor parameters to access the data. This keeps screens loosely connected and easy to manage.

Practice

1. What is the main purpose of passing data between screens in a Flutter app?

easy

A. To change the app's theme colors dynamically

B. To store data permanently on the device

C. To improve the app's startup speed

D. To share information as the user moves from one screen to another

Solution

1. Step 1: Understand screen navigation

   When users move between screens, apps often need to share information to keep context.

2. Step 2: Identify the role of data passing

   Passing data allows the next screen to display or use information from the previous screen.

3. Final Answer:

   To share information as the user moves from one screen to another -> Option D

4. Quick Check:

   Passing data = share info between screens [OK]

Hint: Passing data shares info between screens during navigation [OK]

Common Mistakes:

• Confusing data passing with theme or style changes
• Thinking data passing stores data permanently
• Assuming data passing speeds up app startup

2. Which Flutter code snippet correctly passes a string "Hello" to a new screen called DetailScreen?

easy

A. Navigator.push(context, MaterialPageRoute(builder: (context) => DetailScreen("Hello")));

B. Navigator.push(context, MaterialPageRoute(builder: (context) => DetailScreen));

C. Navigator.push(context, MaterialPageRoute(builder: (context) => DetailScreen(data: "Hello")));

D. Navigator.push(context, MaterialPageRoute(builder: (context) => DetailScreen.data("Hello")));

Solution

1. Step 1: Check constructor usage

   Passing data requires calling the screen's constructor with named or positional parameters.

2. Step 2: Verify syntax correctness

   Navigator.push(context, MaterialPageRoute(builder: (context) => DetailScreen(data: "Hello"))); correctly calls DetailScreen with named parameter data: "Hello" inside the builder.

3. Final Answer:

   Navigator.push(context, MaterialPageRoute(builder: (context) => DetailScreen(data: "Hello"))); -> Option C

4. Quick Check:

   Correct constructor call = Navigator.push(context, MaterialPageRoute(builder: (context) => DetailScreen(data: "Hello"))); [OK]

Hint: Use constructor with named params inside MaterialPageRoute builder [OK]

Common Mistakes:

• Omitting parentheses after DetailScreen
• Passing data without parameter name when required
• Using incorrect method calls on DetailScreen

3. Given this code, what will be displayed on the DetailScreen?

class DetailScreen extends StatelessWidget {
  final String message;
  DetailScreen({required this.message});

  @override
  Widget build(BuildContext context) {
    return Scaffold(
      body: Center(child: Text(message)),
    );
  }
}

// Navigation call:
Navigator.push(context, MaterialPageRoute(builder: (context) => DetailScreen(message: "Welcome")));

medium

A. An empty screen

B. Text widget showing "Welcome"

C. Error because message is not passed

D. Text widget showing "message" literally

Solution

1. Step 1: Analyze constructor parameter

   DetailScreen requires a String message passed via constructor, which is done correctly with "Welcome".

2. Step 2: Check build method output

   The build method shows a Text widget displaying the message variable, so it will show "Welcome".

3. Final Answer:

   Text widget showing "Welcome" -> Option B

4. Quick Check:

   Passed message = displayed text [OK]

Hint: Passed constructor data shows in Text widget [OK]

Common Mistakes:

• Assuming message is not passed causes error
• Thinking Text shows variable name instead of value
• Ignoring the required keyword in constructor

4. What is wrong with this code snippet for passing data?

Navigator.push(context, MaterialPageRoute(builder: (context) => DetailScreen));

medium

A. DetailScreen is missing parentheses to call its constructor

B. Navigator.push cannot be used for navigation

C. MaterialPageRoute should not have a builder

D. Context is not needed in Navigator.push

Solution

1. Step 1: Check DetailScreen usage

   DetailScreen is a class and must be instantiated by calling its constructor with parentheses.

2. Step 2: Identify missing constructor call

   Without parentheses, DetailScreen is a type, not an instance, causing a syntax error.

3. Final Answer:

   DetailScreen is missing parentheses to call its constructor -> Option A

4. Quick Check:

   Constructor call needs parentheses [OK]

Hint: Always add () to call a widget constructor [OK]

Common Mistakes:

• Forgetting parentheses after widget class name
• Misunderstanding Navigator.push usage
• Thinking context is optional in navigation

5. You want to pass a user ID (integer) from HomeScreen to ProfileScreen and display it. Which approach correctly passes and uses this data?

hard

A. Pass userId via ProfileScreen constructor and display it in a Text widget

B. Store userId in a global variable and access it directly in ProfileScreen

C. Use Navigator.pop to send userId to ProfileScreen

D. Pass userId as a parameter to Navigator.pop

Solution

1. Step 1: Understand data passing direction

   Navigator.push sends data forward to a new screen via constructor parameters.

2. Step 2: Identify correct data usage

   Passing userId via ProfileScreen constructor and displaying it in a Text widget is the proper way.

3. Step 3: Eliminate incorrect options

   Global variables are discouraged; Navigator.pop sends data back, not forward.

4. Final Answer:

   Pass userId via ProfileScreen constructor and display it in a Text widget -> Option A

5. Quick Check:

   Push + constructor = pass data forward [OK]

Hint: Use constructor params to pass data forward between screens [OK]

Common Mistakes:

• Using Navigator.pop to send data forward
• Relying on global variables for passing data
• Passing data as parameters to Navigator.pop