Hero animations in Flutter - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is a Hero animation in Flutter?

A Hero animation is a smooth animation that connects a widget from one screen to another, making it look like the widget flies between screens.

beginner

How do you identify widgets that participate in a Hero animation?

You wrap the widgets with a Hero widget and give them the same unique tag to link them across screens.

beginner

What property must be the same on Hero widgets to animate between screens?

The 'tag' property must be the same on Hero widgets on both the source and destination screens.

intermediate

Can Hero animations work with any widget?

Yes, Hero animations can work with any widget, but the widget should be visually similar on both screens for a smooth effect.

advanced

What happens if two Hero widgets have the same tag but are not on consecutive routes?

The Hero animation only works between the current route and the next route. If the tags match but routes are not consecutive, the animation won't run.

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

A To create a smooth animation between two screens for a shared widget

B To handle user input events

C To manage app state

D To load images asynchronously

Hero widgets create smooth animations for shared widgets between screens.

Which property must match for Hero widgets to animate correctly?

A key

B id

C tag

D name

The 'tag' property links Hero widgets across screens for animation.

Where do you place the Hero widget in your widget tree?

A Only in the source screen

B Around the widget you want to animate

C Only in the destination screen

D Around the entire app

Wrap the widget you want to animate with Hero on both source and destination screens.

What happens if Hero widgets have different tags on source and destination screens?

A The animation fails and no transition occurs

B The widgets swap places instantly

C The app crashes

D The animation runs normally

Hero animations require matching tags; otherwise, no animation happens.

Can Hero animations be used with images?

A Only buttons can be used

B No, only text widgets can be used

C Only icons can be used

D Yes, images can be wrapped in Hero widgets

Any widget, including images, can be wrapped in Hero for animations.

Explain how to implement a Hero animation between two Flutter screens.

Think about linking widgets visually across screens.

What are the key benefits of using Hero animations in mobile apps?

Consider how animations help users understand screen changes.

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