Route transition animations in Angular - Mini Project: Build & Apply

Route transition animations

📖 Scenario: You are building a simple Angular app with two pages. You want to add smooth animations when switching between these pages to improve user experience.

🎯 Goal: Create route transition animations that fade pages in and out when navigating between routes.

📋 What You'll Learn

Create a basic Angular app with two routes

Define a trigger for route animations

Apply fade in and fade out animations on route changes

Use Angular's animation module and router outlet with animation binding

💡 Why This Matters

🌍 Real World

Route transition animations improve user experience by making page changes smooth and visually appealing in web apps.

💼 Career

Understanding Angular route animations is useful for frontend developers building modern, polished single-page applications.

1

Set up routes and components

Create two components named HomeComponent and AboutComponent. Then, set up the Angular router with two routes: '' for HomeComponent and 'about' for AboutComponent. Import RouterModule and configure it with these routes in AppModule.

Angular

// Create HomeComponent and AboutComponent
// Set up routes array with path '' for HomeComponent and path 'about' for AboutComponent
// Import RouterModule and call RouterModule.forRoot(routes) in imports array of AppModule

Hint

Define two simple components with templates. Then create a routes array with two route objects. Import RouterModule and call RouterModule.forRoot(routes) in the imports array of AppModule.

2

Add animation trigger and import BrowserAnimationsModule

Import BrowserAnimationsModule from @angular/platform-browser/animations and add it to the imports array in AppModule. Then, create an animation trigger named routeAnimations that defines a simple fade transition between any two states using Angular's trigger, transition, style, and animate functions.

Angular

import { BrowserAnimationsModule } from '@angular/platform-browser/animations';
import { trigger, transition, style, animate } from '@angular/animations';

// Add BrowserAnimationsModule to imports array
// Create a trigger named routeAnimations with fade in/out transitions

Hint

Import BrowserAnimationsModule and add it to imports. Then define routeAnimations using trigger with a transition that fades opacity from 0 to 1 over 300ms.

3

Bind animation trigger to router outlet

In the main app component template, add a <router-outlet> element. Bind the @routeAnimations trigger to the router outlet by adding [@routeAnimations]="prepareRoute(outlet)" and a template reference variable #outlet="outlet". Then, in the app component class, add a method prepareRoute that returns the activatedRouteData['animation'] from the router outlet.

Angular

@Component({
  selector: 'app-root',
  template: `
    
  `,
  animations: [routeAnimations]
})
export class AppComponent {
  prepareRoute(outlet: any) {
    // Your code here
  }
}

Hint

Bind @routeAnimations to router-outlet with a template variable #outlet="outlet". Add prepareRoute method to return the animation data from the outlet's activated route. Add data: { animation: 'HomePage' } and data: { animation: 'AboutPage' } to routes.

4

Complete app component and bootstrap

Ensure the AppComponent is declared and bootstrapped in AppModule. The app component template should contain the router outlet with the animation binding. This completes the setup for route transition animations.

Angular

// Ensure AppComponent is declared and bootstrapped in AppModule
// The template contains router-outlet with animation binding

Hint

Make sure AppComponent is declared and bootstrapped in AppModule. The app component template should have the router outlet with the animation binding.

Practice

1. What is the main purpose of route transition animations in Angular?

easy

A. To speed up the loading time of routes

B. To smoothly show changes when navigating between pages

C. To prevent users from clicking links

D. To change the URL format automatically

Solution

1. Step 1: Understand what route transition animations do

   They create smooth visual effects when moving from one page to another in an Angular app.

2. Step 2: Identify the main benefit

   This helps users see the change clearly and makes the app feel more polished.

3. Final Answer:

   To smoothly show changes when navigating between pages -> Option B

4. Quick Check:

   Route animations = smooth page changes [OK]

Hint: Animations = smooth visual changes between routes [OK]

Common Mistakes:

• Thinking animations speed up loading
• Confusing animations with URL changes
• Believing animations block clicks

2. Which Angular module must you import to use route transition animations?

easy

A. BrowserAnimationsModule

B. HttpClientModule

C. FormsModule

D. RouterModule

Solution

1. Step 1: Identify the module for animations

   Angular requires BrowserAnimationsModule to enable animation features.

2. Step 2: Confirm other modules' roles

   HttpClientModule is for HTTP calls, FormsModule for forms, RouterModule for routing but not animations.

3. Final Answer:

   BrowserAnimationsModule -> Option A

4. Quick Check:

   Animations need BrowserAnimationsModule [OK]

Hint: Animations need BrowserAnimationsModule import [OK]

Common Mistakes:

• Importing RouterModule instead of BrowserAnimationsModule
• Forgetting to import any animation module
• Confusing FormsModule with animation needs

3. Given this animation trigger in Angular:

trigger('routeAnimations', [
  transition('* <=> *', [
    style({ opacity: 0 }),
    animate('300ms ease-in', style({ opacity: 1 }))
  ])
])

What happens when the route changes?

medium

A. The page reloads without animation

B. The new page slides in from the left instantly

C. The new page fades in from transparent to visible over 300ms

D. The old page fades out but new page appears instantly

Solution

1. Step 1: Analyze the animation steps

   The style starts with opacity 0 (invisible), then animates to opacity 1 (visible) over 300ms.

2. Step 2: Understand the transition

   The transition applies to any route change ('* <=> *'), so the new page fades in smoothly.

3. Final Answer:

   The new page fades in from transparent to visible over 300ms -> Option C

4. Quick Check:

   Opacity 0 to 1 = fade in [OK]

Hint: Opacity 0 to 1 means fade in effect [OK]

Common Mistakes:

• Thinking it slides instead of fades
• Assuming instant change without animation
• Confusing fade out with fade in

4. Identify the error in this Angular route animation code snippet:

@Component({
  animations: [
    trigger('routeAnimations', [
      transition('HomePage => AboutPage', [
        animate('500ms ease-in')
      ])
    ])
  ]
})
export class AppComponent {}

medium

A. transition syntax requires '*' wildcard instead of page names

B. Incorrect trigger name, should be 'routeAnimation' singular

C. animate() duration must be in seconds, not milliseconds

D. Missing style() before animate() in transition

Solution

1. Step 1: Check animation steps in transition

   Angular animations usually start with style() to set initial state before animate().

2. Step 2: Confirm if style() is required

   Without style(), Angular animates from current state, which may cause unexpected behavior.

3. Final Answer:

   Missing style() before animate() in transition -> Option D

4. Quick Check:

   Animations need style() before animate() [OK]

Hint: Always start transition with style() before animate() [OK]

Common Mistakes:

• Skipping style() causes animation issues
• Confusing trigger naming conventions
• Wrong time units in animate()

5. How can you trigger different animations for specific routes in Angular using route transition animations?

hard

A. By setting a unique animation state in each route's data and using it in the animation trigger

B. By changing the component selector dynamically during navigation

C. By disabling animations and manually adding CSS classes on route change

D. By using multiple RouterOutlet elements for each route

Solution

1. Step 1: Understand route data usage

   Angular routes can have a data property where you define an animation state string for each route.

2. Step 2: Use the animation state in the trigger

   The animation trigger reads this state to decide which animation to run on route change.

3. Step 3: Confirm other options are incorrect

   Changing selectors or disabling animations is not standard; multiple RouterOutlets are for nested routes, not animations.

4. Final Answer:

   By setting a unique animation state in each route's data and using it in the animation trigger -> Option A

5. Quick Check:

   Route data controls animation states [OK]

Hint: Use route data to assign animation states [OK]

Common Mistakes:

• Trying to change component selectors dynamically
• Manually toggling CSS instead of Angular animations
• Using multiple RouterOutlets incorrectly