Bird
Raised Fist0
Fluttermobile~5 mins

Hero animations in Flutter

Choose your learning style10 modes available
Introduction

Hero animations help make screen changes smooth by moving a widget from one page to another. This makes the app feel connected and natural.

When you want to show a picture or item moving from a list to a detail page.
When you want to highlight a button or icon that appears on two screens.
When you want to create a smooth transition between two related screens.
When you want to keep user focus on an element during navigation.
When you want to add polish and professionalism to your app's navigation.
Syntax
Flutter
Hero(
  tag: 'uniqueTag',
  child: WidgetToAnimate(),
)

The tag must be the same on both source and destination widgets.

The child is the widget that will animate between screens.

Examples
This wraps an image with a Hero widget using the tag 'imageHero'.
Flutter
Hero(
  tag: 'imageHero',
  child: Image.network('https://example.com/pic.jpg'),
)
This wraps an icon with a Hero widget using the tag 'iconHero'.
Flutter
Hero(
  tag: 'iconHero',
  child: Icon(Icons.star, size: 50),
)
Sample App

This app shows a small owl image on the first page. When you tap it, the image smoothly grows and moves to the second page. This is done by wrapping the image in a Hero widget with the same tag on both pages.

Flutter
import 'package:flutter/material.dart';

void main() => runApp(const MyApp());

class MyApp extends StatelessWidget {
  const MyApp({super.key});

  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      title: 'Hero Animation Demo',
      home: const FirstPage(),
    );
  }
}

class FirstPage extends StatelessWidget {
  const FirstPage({super.key});

  @override
  Widget build(BuildContext context) {
    return Scaffold(
      appBar: AppBar(title: const Text('First Page')),
      body: Center(
        child: GestureDetector(
          onTap: () {
            Navigator.push(
              context,
              MaterialPageRoute(builder: (_) => const SecondPage()),
            );
          },
          child: Hero(
            tag: 'hero-image',
            child: ClipRRect(
              borderRadius: BorderRadius.circular(8),
              child: Image.network(
                'https://flutter.github.io/assets-for-api-docs/assets/widgets/owl.jpg',
                width: 150,
              ),
            ),
          ),
        ),
      ),
    );
  }
}

class SecondPage extends StatelessWidget {
  const SecondPage({super.key});

  @override
  Widget build(BuildContext context) {
    return Scaffold(
      appBar: AppBar(title: const Text('Second Page')),
      body: Center(
        child: Hero(
          tag: 'hero-image',
          child: Image.network(
            'https://flutter.github.io/assets-for-api-docs/assets/widgets/owl.jpg',
            width: 300,
          ),
        ),
      ),
    );
  }
}
OutputSuccess
Important Notes

Make sure the tag is unique in the app and matches exactly on both widgets.

The Hero animation works best with images or shapes that look similar on both screens.

You can customize the animation by wrapping the Hero's child with other widgets like ClipRRect for rounded corners.

Summary

Hero animations create smooth transitions by moving a widget between screens.

Use the same tag on both widgets to link them.

They improve user experience by making navigation feel natural and connected.

Practice

(1/5)
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
Recommended

Ready to prove it?

Pass the test and this pattern moves unknown strong while earning +1 Grip toward your certificate.

10 questions~5 mineasy hard