Passing data between screens in Flutter - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is the common way to pass data from one screen to another in Flutter?

You pass data by sending it as arguments when navigating using Navigator.push(). The receiving screen accepts the data through its constructor.

intermediate

How do you retrieve data returned from a screen after it is popped in Flutter?

Use the Future returned by Navigator.push() and await it. The popped screen can return data using Navigator.pop(context, data).

beginner

Why should you avoid using global variables to share data between screens?

Global variables can cause unexpected bugs and make your app harder to maintain. Passing data explicitly keeps screens independent and easier to test.

beginner

What widget is used to navigate to a new screen in Flutter?

Navigator.push() is used to add a new screen on top of the navigation stack.

intermediate

Explain how to pass multiple pieces of data to a new screen.

Create a class or use named parameters in the screen's constructor to accept multiple data items. Pass them all when calling Navigator.push().

Which Flutter method is used to navigate to a new screen?

A build()

B Navigator.push()

C setState()

D Navigator.pop()

Navigator.push() adds a new screen on top of the current one.

How do you pass data to a new screen in Flutter?

A Through the new screen's constructor

B Using setState()

C By calling Navigator.pop()

D Using global variables only

You pass data by providing it as arguments to the new screen's constructor.

How can a screen return data back to the previous screen?

A By calling build()

B Using Navigator.push()

C Using setState()

D Using Navigator.pop(context, data)

Navigator.pop() can send data back to the previous screen.

What type does Navigator.push() return?

A Future

B void

C int

D String

Navigator.push() returns a Future that completes when the new screen is popped.

Why is passing data via constructors preferred over global variables?

A Global variables are faster

B Global variables are safer

C It keeps screens independent and easier to maintain

D Constructors cannot pass data

Passing data explicitly avoids bugs and improves code clarity.

Describe the steps to pass data from one screen to another in Flutter.

Think about how you send a package to a friend and how they open it.

Explain how to get data back from a screen after it closes.

Like asking a friend to bring you something back when they return.

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