cms

Tag: Angular Standalone

  • Building a Generic Loading Service & HTTP Interceptor in an Angular Standalone

    Building a Generic Loading Service & HTTP Interceptor in an Angular Standalone

    Loading generic component

    Problem & Goal

    In many Angular applications, developers manually control loading indicators inside each component. While this works for small projects, it quickly becomes repetitive, error-prone, and hard to maintain as the codebase grows.

    A better approach is to centralize loading state management. By using a generic loading service combined with an HTTP interceptor, we can automatically track when requests start and finish — showing a global progress spinner without writing extra code in every component.

    We’ll also add a configurable flag to skip the progress spinner for certain requests — useful for silent background calls or analytics pings that don’t need to interrupt the user experience.

    Our goals are:

    1. Centralized Loading State – Manage loading indicators in one place instead of scattering logic across components.
    2. Automatic Triggering – Show/hide a spinner automatically for all HTTP requests.
    3. Configurable Behavior – Allow opting out of the spinner per-request using a flag.
    4. Standalone-Friendly – Ensure the solution works seamlessly in Angular standalone projects without relying on NgModules.

    Creating the Loader Component

    Before we set up our HTTP interceptor, we first need a Loader Component that can display a progress spinner overlay whenever our application is performing network requests. This will serve as the visual feedback for the user, showing that something is happening in the background.

    We’ll use Angular Material’s <mat-progress-spinner> because it’s lightweight, accessible, and easy to style.

    Loader Template

    @if (loadingService.isLoading$ | async) {
      <div class="loader-overlay">
        <mat-progress-spinner
          class="loading-spinner"
          mode="indeterminate"
          diameter="64"
        ></mat-progress-spinner>
      </div>
    }

    How it works:

    • We’re using Angular’s new template syntax @if to conditionally display the loader only when the isLoading$ observable emits true.
    • The mat-progress-spinner is set to indeterminate mode so it spins continuously until the request completes.
    • Wrapping it in a .loader-overlay div ensures it’s centered and blocks user interaction while active.

    Loader Component Class

    import { Component, inject } from '@angular/core';
    import { LoadingService } from '../services/loading.service';
    
    @Component({
      selector: 'app-loader',
      standalone: true,
      templateUrl: './loader.component.html',
      styleUrls: ['./loader.component.scss'],
    })
    export class LoaderComponent {
      loadingService = inject(LoadingService);
    }

    The component is kept intentionally simple — it just injects the LoadingService and binds to its isLoading$ observable.

    Loader Styles

    .loader-overlay {
      position: fixed;
      width: 100%;
      height: 100%;
      left: 0;
      top: 0;
      background-color: rgba(6, 27, 44, 0.2);
      z-index: 9999;
      display: flex;
      flex-direction: column;
      align-items: center;
      justify-content: center;
    }
    
    .loading-spinner {
      height: 64px;
    }

    This styling ensures the loader:

    • Covers the entire screen.
    • Has a subtle dark overlay to focus user attention.
    • Centers the spinner both vertically and horizontally.

    With the loader component ready, the next step is to create a Loading Service that will control when this spinner is shown — and later, we’ll hook it into an HTTP interceptor so it all works automatically.

    Creating the Loading Service

    Now that we have our loader component, we need a way to control when it appears. The LoadingService will be our central state manager for tracking ongoing HTTP requests.

    Instead of just toggling a boolean, this service uses a counter (apiCount) to handle multiple simultaneous API calls. That way, the loader won’t disappear until all requests have finished.

    Loading Service Code

    import { Injectable } from '@angular/core';
    import { BehaviorSubject } from 'rxjs';
    
    @Injectable({
      providedIn: 'root',
    })
    export class LoadingService {
      // Tracks the number of ongoing API calls
      private apiCount = 0;
    
      private isLoadingSubject = new BehaviorSubject<boolean>(false);
      isLoading$ = this.isLoadingSubject.asObservable();
    
      /** Show loader (when an API starts) */
      showLoader() {
        if (this.apiCount === 0) {
          this.isLoadingSubject.next(true);
        }
        this.apiCount++;
      }
    
      /** Hide loader (when an API completes) */
      hideLoader() {
        if (this.apiCount > 0) {
          this.apiCount--;
        }
        if (this.apiCount === 0) {
          this.isLoadingSubject.next(false);
        }
      }
    
      /** Force hide the loader (e.g., when polling stops) */
      forceHideLoader() {
        this.apiCount = 0;
        this.isLoadingSubject.next(false);
      }
    }

    How it works

    • apiCount keeps track of the number of ongoing API calls.
    • isLoadingSubject emits true when the first API starts and false only when the last one completes.
    • showLoader() increments the counter and turns on the spinner if it’s the first request.
    • hideLoader() decrements the counter and hides the spinner when all requests are done.
    • forceHideLoader() immediately resets the counter and hides the loader — handy for scenarios like stopping background polling.

    With the loader component and loading service ready, the next step is to create an HTTP interceptor that will automatically call showLoader() and hideLoader() for us — and respect a configurable flag to skip the loader for certain requests.

    Creating the HTTP Interceptor

    Manually calling showLoader() and hideLoader() in every component would defeat the purpose of our centralized solution. Instead, we’ll use an HTTP interceptor to hook into every request and response automatically.

    This interceptor will:

    1. Call showLoader() when a request starts.
    2. Call hideLoader() when the request finishes (success or error).
    3. Respect a skip flag (X-Skip-Loader header) so certain requests won’t trigger the loader.

    Interceptor Code

    import { HttpInterceptorFn } from '@angular/common/http';
    import { inject } from '@angular/core';
    import { LoadingService } from '../../services/loading/loading.service';
    import { finalize } from 'rxjs';
    
    export const loaderInterceptor: HttpInterceptorFn = (req, next) => {
      const loadingService = inject(LoadingService);
    
      // If this request has the custom header, skip showing the loader
      const shouldSkipLoader = req.headers.has('X-Skip-Loader');
    
      if (!shouldSkipLoader) {
        loadingService.showLoader();
      }
    
      return next(req).pipe(
        finalize(() => {
          if (!shouldSkipLoader) {
            loadingService.hideLoader();
          }
        })
      );
    };

    How it works

    • Skip flag: By adding a custom header X-Skip-Loader to any HTTP request, we tell the interceptor not to show the spinner for that request. This is useful for silent background calls like analytics pings or cache warmups.
    • Automatic tracking: The interceptor calls showLoader() before passing the request forward, and uses finalize() to guarantee hideLoader() runs when the request completes, fails, or is canceled.
    • Standalone-friendly: This uses Angular’s HttpInterceptorFn functional API, which works seamlessly in standalone projects without the need for traditional @Injectable() class-based interceptors.

    Example — Skipping the Loader for a Request

    this.http.get('/api/analytics', {
      headers: { 'X-Skip-Loader': '' }
    }).subscribe();

    With the loader component, loading service, and interceptor in place, you now have a fully automated, configurable global loading indicator in your Angular standalone project.

    In the next part, we’ll bring everything together by registering the interceptor and adding the loader component to the app so it works across all pages.

    Putting It All Together

    We now have:

    • A Loader Component that displays a progress spinner overlay.
    • A Loading Service that tracks ongoing HTTP requests.
    • An HTTP Interceptor that automatically triggers the loader and supports skipping it with a custom header.

    Let’s integrate these pieces into our Angular standalone app.

    Register the Interceptor

    In a standalone Angular project, interceptors are added in the providers array of bootstrapApplication.

    import { bootstrapApplication } from '@angular/platform-browser';
    import { provideHttpClient, withInterceptors } from '@angular/common/http';
    import { AppComponent } from './app/app.component';
    import { loaderInterceptor } from './app/interceptors/loader/loader.interceptor';
    
    bootstrapApplication(AppComponent, {
      providers: [
        provideHttpClient(withInterceptors([loaderInterceptor])),
      ],
    }).catch((err) => console.error(err));

    This ensures every HTTP request in your app passes through the loaderInterceptor.

    Add the Loader Component to the Root Template

    Place the loader component inside your AppComponent template so it can be displayed globally:

    <app-loader></app-loader>
    <router-outlet></router-outlet>

    Since the LoaderComponent listens to LoadingService.isLoading$, it will automatically appear and disappear without any additional wiring in individual components.

    Skipping the Loader for Certain Requests

    For requests where you don’t want to block the UI with a spinner, simply include the X-Skip-Loader header:

    this.http.get('/api/analytics', {
      headers: { 'X-Skip-Loader': '' }
    }).subscribe();

    This keeps the UI uninterrupted for silent background operations.

    Final Thoughts

    With just a few pieces — a loader component, a loading service, and a functional HTTP interceptor — we’ve created a centralized, configurable global loading indicator for an Angular standalone project.

    The benefits are clear:

    • No more repetitive spinner logic in multiple components.
    • Consistent user experience for all network calls.
    • Fine-grained control to skip the loader when needed.

    This pattern is clean, scalable, and fully compatible with Angular’s modern standalone architecture.

  • Using Lottie Icons in Angular Standalone Projects

    Using Lottie Icons in Angular Standalone Projects

    Introduction

    Animations can add a lot of life to a web app — but let’s be honest, Animations can bring a web app to life — whether it’s a subtle loading spinner or a bold hero icon, they make your UI feel smoother and more modern. But traditional formats like GIFs or sprite sheets? Not so great. They’re heavy, not scalable, and kind of stuck in the past.

    That’s where Lottie comes in. Lottie lets you render beautiful, high-quality animations using small JSON files. They’re lightweight, resolution-independent, and easy to control — a perfect fit for today’s fast, interactive frontends.

    In this post, I’ll walk you through how to set up and use Lottie animations in Angular, using a clean and modern approach. It’s quick to get started, and once you do, you’ll probably never want to go back to static icons again.

    Here’s what you’ll learn:

    • What Lottie animations are and why they’re awesome for modern UIs
    • How to set up Lottie in your Angular standalone project
    • How to add and reuse animations in your components

    Let’s jump in and make your app a little more fun ✨

    What Lottie animations are and why they’re awesome for modern UIs

    Lottie is an open-source animation library developed by Airbnb that lets you render animations created in Adobe After Effects (exported via Bodymovin) as real-time, vector-based animations in your app — using just JSON.

    Unlike GIFs or video files, Lottie animations are:

    • Lightweight – they load quickly and don’t bloat your bundle size.
    • Scalable – no quality loss on high-DPI screens.
    • Interactive – you can control playback, respond to user actions, or even sync them with state changes.

    They’re perfect for:

    • Loading spinners
    • Button feedback
    • Empty states and onboarding screens
    • Decorative illustrations

    Most developers use LottieFiles — a massive library of free (and premium) animations you can browse, customize, and export directly as JSON files for use in your app.

    So instead of using clunky image assets or reinventing animation from scratch, Lottie gives you plug-and-play motion design — and your users will feel the difference.

    How to set up Lottie in your Angular standalone project

    Once you’ve got your Angular project set up, adding Lottie is pretty straightforward. We’ll be using the official Angular wrapper for Lottie: ngx-lottie.

    Install the necessary packages:

    npm install lottie-web ngx-lottie

    Next, configure the Lottie player globally using provideLottieOptions. This can go in your app.config.ts:

    import {
      ApplicationConfig,
      provideBrowserGlobalErrorListeners,
      provideZoneChangeDetection,
    } from '@angular/core';
    import { provideRouter } from '@angular/router';
    import { provideLottieOptions } from 'ngx-lottie';
    import player from 'lottie-web';
    
    import { routes } from './app.routes';
    
    export const appConfig: ApplicationConfig = {
      providers: [
        provideBrowserGlobalErrorListeners(),
        provideZoneChangeDetection({ eventCoalescing: true }),
        provideRouter(routes),
        provideLottieOptions({
          player: () => player,
        }),
      ],
    };

    And that’s it — Lottie is now wired up and ready to use in your components!

    How to Add and Reuse Animations in Your Components

    Now that Lottie is wired up, let’s make it easy to drop animations anywhere in your app.

    Instead of repeating the same Lottie config in every component, we’ll create a dedicated LottieIconComponent. This keeps things clean and lets you reuse animations by just passing in a few inputs like the path, size, and autoplay settings.

    Creating the LottieIconComponent

    To get started, create a new standalone component:

    ng generate component lottie-icon

    Set up the component using signal inputs

    Let’s wire it up to accept a path to the animation, along with optional size and behavior flags.

    // lottie-icon.ts
    import { Component, computed, input } from '@angular/core';
    import { AnimationOptions, LottieComponent } from 'ngx-lottie';
    
    @Component({
      selector: 'app-lottie-icon',
      imports: [LottieComponent],
      templateUrl: './lottie-icon.html',
      styleUrl: './lottie-icon.css',
    })
    export class LottieIcon {
      path = input<string>('');
      width = input<string>('100px');
      height = input<string>('100px');
      loop = input<boolean>(true);
      autoplay = input<boolean>(true);
    
      readonly options = computed<AnimationOptions>(() => ({
        path: this.path(),
        loop: this.loop(),
        autoplay: this.autoplay(),
      }));
    }

    <!-- lottie-icon.html -->
    <ng-lottie
      [options]="options()"
      [styles]="{ width: width(), height: height() }"
    ></ng-lottie>

    Use It Anywhere in Your App

    Before using your Lottie icon, make sure your JSON animation file is placed where Angular can serve it statically.

    📁 Put Your Icon in the Public Folder

    Drop your animation file into the public/icons directory. For example:

    public/icons/lottie-icon.json

    Files in the public/ folder are served as-is at the root of your app, so the URL to this file will be /icons/lottie-icon.json.

    You can now drop your Lottie icons into any component where you want a bit of motion or visual feedback. They’re perfect for things like loading states, empty screens, confirmation messages, or just to add a little personality to your UI.

    Here’s how you can use the reusable component:

    <app-lottie-icon 
      [path]="'/icons/lottie-icon.json'" 
      [width]="'150px'" 
      [height]="'150px'" 
      [loop]="true" 
      [autoplay]="true">
    </app-lottie-icon>

    This example loads an animation from your /public/icons/ folder, sizes it to 150×150 pixels, and sets it to autoplay in a loop. You can easily switch out the path to show different icons, and adjust the width, height, loop, or autoplay settings as needed.

    🧵 In Summary

    Lottie makes it super easy to add sleek, scalable animations to your Angular app — and with a reusable component setup, you don’t have to repeat yourself. Whether you’re adding a fun touch to a button or showing a loading state with flair, Lottie helps your UI feel more modern and alive.

    Now you’ve got the setup, the component, and the flexibility — go ahead and bring your UI to life!