Hero animations in Flutter - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ ui_behavior

intermediate

What happens when two Hero widgets have different tags?

Consider two screens each containing a Hero widget. The Hero on the first screen has tag 'hero1', and the Hero on the second screen has tag 'hero2'. What will happen when navigating between these screens?

A The app will crash due to tag mismatch.

B The Hero animation will run smoothly between the two widgets despite different tags.

C The Hero animation will not run; the widgets will just appear without animation.

D The Hero widgets will animate but with a flicker effect.

💡 Hint

Hero animations require matching tags to link widgets across screens.

Hero animations only work when the Hero widgets on both screens share the same tag. Different tags mean Flutter cannot match the widgets, so no animation occurs.

❓ lifecycle

intermediate

When does the Hero animation start during navigation?

At what point in the navigation lifecycle does the Hero animation begin when pushing a new route?

A After both the source and destination widgets have been built and laid out.

B Immediately after the new route is pushed but before the new screen builds.

C Before the source widget is removed from the widget tree.

D Only after the new route's build method completes.

💡 Hint

Think about when Flutter can measure widget positions for animation.

The Hero animation starts after both source and destination widgets are built and laid out so Flutter knows their positions to animate between them.

📝 Syntax

advanced

Identify the correct Hero widget usage

Which of the following Flutter code snippets correctly implements a Hero widget wrapping an Image with tag 'profilePic'?

A Hero(tag: 'profilePic', child: Image.asset('assets/pic.png'))

B Hero(child: Image.asset('assets/pic.png'), tag: 'profilePic')

C Hero(tag: 'profilePic', child: Image('assets/pic.png'))

D Hero(tag: profilePic, child: Image.asset('assets/pic.png'))

💡 Hint

Check the order of parameters and tag type.

Option A uses correct parameter order and a string tag. Option A has parameters reversed (though Flutter allows named parameters in any order, so B is valid). Option A uses an undefined variable profilePic instead of a string. Option A uses Image constructor incorrectly.

🔧 Debug

advanced

Why does this Hero animation cause a jump instead of smooth transition?

Given two screens with Hero widgets sharing the same tag, the animation jumps abruptly instead of smoothly transitioning. What is the most likely cause?

Flutter

Screen 1:
Hero(tag: 'logo', child: Container(width: 100, height: 100, color: Colors.blue))

Screen 2:
Hero(tag: 'logo', child: Container(width: 200, height: 200, color: Colors.blue))

A The Hero widgets have different tags causing the jump.

B The Hero widgets have different sizes causing the jump.

C The Hero widgets are missing a Material ancestor.

D The Hero widgets have different colors causing the jump.

💡 Hint

Hero animations can handle size changes but abrupt jumps usually mean size difference without smooth scaling.

Different sizes between source and destination Hero widgets can cause the animation to jump if the transition is not smooth. Colors do not cause jumps, and tags are the same here. Material ancestor absence causes errors but not jumps.

🧠 Conceptual

expert

What is the role of FlightShuttleBuilder in Hero animations?

In Flutter's Hero widget, what does the FlightShuttleBuilder property control?

A It disables the Hero animation when set to null.

B It controls the duration of the Hero animation.

C It specifies the curve used for the Hero animation.

D It defines the widget shown during the Hero's flight animation between screens.

💡 Hint

Think about customizing the look of the Hero while it moves.

FlightShuttleBuilder lets you customize the widget displayed during the Hero's transition animation, allowing different visuals than the source or destination widgets.

Practice

1. What is the main purpose of a Hero widget in Flutter?

easy

A. To create smooth animations between two screens by linking widgets with the same tag

B. To manage state across multiple widgets

C. To handle user input events

D. To fetch data from the internet asynchronously

Solution

1. Step 1: Understand Hero widget role

   The Hero widget is designed to animate a widget from one screen to another smoothly.

2. Step 2: Identify correct purpose

   It links widgets on different screens using the same tag to create a seamless transition.

3. Final Answer:

   To create smooth animations between two screens by linking widgets with the same tag -> Option A

4. Quick Check:

   Hero widget = smooth screen transition [OK]

Hint: Hero widgets link by tag for smooth screen animations [OK]

Common Mistakes:

• Confusing Hero with state management widgets
• Thinking Hero handles user input
• Assuming Hero fetches data

2. Which of the following is the correct way to define a Hero widget with a tag of 'profilePic'?

easy

A. Hero(tag: profilePic, child: Image.asset('pic.png'))

B. Hero(child: Image.asset('pic.png'), tag: profilePic)

C. Hero(tag: 'profilePic', child: Image.asset('pic.png'))

D. Hero('profilePic', child: Image.asset('pic.png'))

Solution

1. Step 1: Check Hero constructor syntax

   The Hero widget requires named parameters: tag and child.

2. Step 2: Validate correct parameter order and types

   Hero(tag: 'profilePic', child: Image.asset('pic.png')) uses named parameters correctly with a string tag and a child widget.

3. Final Answer:

   Hero(tag: 'profilePic', child: Image.asset('pic.png')) -> Option C

4. Quick Check:

   Hero uses named parameters tag and child [OK]

Hint: Use named parameters: tag first, then child [OK]

Common Mistakes:

• Passing tag as positional argument
• Using unquoted tag string
• Swapping tag and child order without names

3. Given this code snippet, what will happen when navigating from Screen A to Screen B?

Screen A:
Hero(tag: 'logo', child: Image.asset('logo.png'))

Screen B:
Hero(tag: 'logo', child: Image.asset('logo_large.png'))

medium

A. The logo image will smoothly animate from Screen A to Screen B, changing size

B. No animation will occur because the images are different

C. The app will crash due to tag conflict

D. The Hero animation will flicker and not complete

Solution

1. Step 1: Understand Hero tag matching

   Hero animations link widgets with the same tag, regardless of child widget differences.

2. Step 2: Predict animation behavior

   The image will animate smoothly from the smaller to the larger version because the tag matches.

3. Final Answer:

   The logo image will smoothly animate from Screen A to Screen B, changing size -> Option A

4. Quick Check:

   Matching tags animate widgets smoothly [OK]

Hint: Same tag triggers animation even if child widgets differ [OK]

Common Mistakes:

• Assuming images must be identical for animation
• Thinking different children cause crashes
• Expecting no animation if child changes

4. What is wrong with this Hero animation code?

Hero(tag: 'avatar', child: Container(color: Colors.blue))

// On next screen
Hero(tag: 'avatar', child: Container(color: Colors.red))

medium

A. The child widgets are not wrapped in Material widgets

B. The Hero animation will fail because Container has no size

C. The Hero widgets have different tags

D. Nothing is wrong; this code works correctly

Solution

1. Step 1: Check Hero child widget requirements

   Hero animations require child widgets to have a defined size to animate properly.

2. Step 2: Analyze Container usage

   Container with only color but no size defaults to zero size, causing animation failure.

3. Final Answer:

   The Hero animation will fail because Container has no size -> Option B

4. Quick Check:

   Hero child needs size to animate [OK]

Hint: Ensure Hero child widgets have size for animation [OK]

Common Mistakes:

• Thinking tag mismatch causes error here
• Assuming Material widget is always required
• Ignoring size requirement of Hero child

5. You want to create a Hero animation for a profile picture that appears in a list and on a detail page. The list shows a small circular avatar, and the detail page shows a larger square image. How should you implement the Hero widgets to ensure a smooth animation?

hard

A. Use different tags for each Hero widget to avoid conflicts

B. Use the same tag but keep both images circular to match shapes exactly

C. Wrap both Hero widgets in Material widgets with different elevation values

D. Use the same tag on both Hero widgets; wrap the small avatar in a ClipOval and the large image in a ClipRRect with border radius zero

Solution

1. Step 1: Use matching tags for Hero animation

   Both Hero widgets must share the same tag to link the animation.

2. Step 2: Handle shape differences smoothly

   Wrap the small avatar in ClipOval for circle shape and the large image in ClipRRect with zero border radius for square shape to animate shape change smoothly.

3. Final Answer:

   Use the same tag on both Hero widgets; wrap the small avatar in a ClipOval and the large image in a ClipRRect with border radius zero -> Option D

4. Quick Check:

   Same tag + shape wrappers = smooth Hero animation [OK]

Hint: Match tags and wrap widgets to animate shape changes [OK]

Common Mistakes:

• Using different tags breaks animation
• Ignoring shape differences causes jumpy animation
• Assuming Material widget fixes shape issues