Hero animations in Flutter - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to wrap the image with a Hero widget using the tag 'hero-image'.

Flutter

Hero(tag: [1], child: Image.asset('assets/picture.png'))

Drag options to blanks, or click blank then click option'

A'heroTag'

B'image-hero'

C'picture'

D'hero-image'

Attempts:

3 left

💡 Hint

Common Mistakes

Using a tag that is not a string.

Using different tags on source and destination widgets.

The Hero widget requires a tag string to identify the shared element. 'hero-image' matches the tag used in both screens.

2fill in blank

medium

Complete the code to navigate to the DetailPage with a hero animation.

Flutter

Navigator.push(context, MaterialPageRoute(builder: (context) => [1]()));

Drag options to blanks, or click blank then click option'

ADetailPage

BHomePage

CMainPage

DSettingsPage

Attempts:

3 left

💡 Hint

Common Mistakes

Navigating to the wrong page without the Hero widget.

Using a page class that does not exist.

To trigger the hero animation, navigate to the DetailPage which contains the matching Hero widget.

3fill in blank

hard

Fix the error in the Hero widget by completing the missing tag value.

Flutter

Hero(tag: [1], child: Icon(Icons.star, size: 50))

Drag options to blanks, or click blank then click option'

A'star-icon'

BIcons.star

C50

DIcon(Icons.star)

Attempts:

3 left

💡 Hint

Common Mistakes

Using a widget or number as the tag.

Leaving the tag empty.

The tag must be a unique string, not an Icon or number. 'star-icon' is a valid tag string.

4fill in blank

hard

Fill both blanks to create a Hero widget with tag 'profile-pic' wrapping a CircleAvatar.

Flutter

Hero(tag: [1], child: CircleAvatar(radius: [2]))

Drag options to blanks, or click blank then click option'

A'profile-pic'

B30

C50

D'avatar'

Attempts:

3 left

💡 Hint

Common Mistakes

Using a wrong tag string.

Using an incorrect radius value.

The tag must be 'profile-pic' and the CircleAvatar radius is 30 for correct sizing.

5fill in blank

hard

Fill all three blanks to create a Hero animation with tag 'logo', wrapping an Image widget with width 100 and height 100.

Flutter

Hero(tag: [1], child: Image.asset('assets/logo.png', width: [2], height: [3]))

Drag options to blanks, or click blank then click option'

A'logo'

B100

C150

D'icon'

Attempts:

3 left

💡 Hint

Common Mistakes

Using different width and height values.

Using a wrong tag string.

The tag is 'logo' and both width and height are 100 for a square image.

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