Components
Data Display
Lottie

Lottie

Use LottieComponent to build consistent, accessible interfaces aligned with the shared design system.

Installation

1. Copy the source code:

  • Source in this monorepo: packages/ui/src/components/lottie.tsx
  • Place in your project: components/ui/lottie.tsx
  • Required utility: lib/utils.ts (for cn helper)

2. Update the import paths to match your project structure.


Usage

import { LottieComponent } from "@hoag/ui/components/lottie";
import animationData from "@/assets/animations/success.json";
 
export default function Demo() {
  return (
    <LottieComponent animationData={animationData} width={160} height={160} />
  );
}

Import

import { LottieComponent } from "@hoag/ui/components/lottie";

Basic Example

Provide your own animation JSON to render a live Lottie preview.

import { LottieComponent } from "@hoag/ui/components/lottie";
import animationData from "@/assets/animations/success.json";
 
export function LottieComponentBasicExample() {
  return (
    <LottieComponent
      animationData={animationData}
      width={180}
      height={180}
      loop={false}
    />
  );
}

Composition Pattern

import { LottieComponent } from "@hoag/ui/components/lottie";
 
export function LottieComponentSection() {
  return (
    <section className="space-y-3">
      <h3 className="text-sm font-medium">Lottie section</h3>
      <LottieComponent />
    </section>
  );
}

Accessibility Checklist

  • Verify semantic roles and ARIA attributes for interactive behavior.
  • Keep keyboard navigation and focus visibility consistent in all states.
  • Ensure color contrast meets accessibility requirements in light and dark themes.
  • Provide screen reader context for dynamic state or content changes.

Testing Checklist

  • Add render tests for default and key variant states.
  • Add interaction tests for callbacks and state transitions.
  • Add visual regression checks for responsive and theme variations.
  • Cover edge states such as loading, empty, disabled, and error.

Production Tips

  • Wrap component logic in feature-level abstractions for domain behavior.
  • Keep visual variants centralized to avoid style drift across screens.
  • Reuse a single import path strategy for simpler refactors.
  • Mirror documented states in Storybook and QA checklists.

Named Exports

  • LottieComponent

API Reference

For authoritative prop signatures and implementation details, inspect:

  • packages/ui/src/components/lottie.tsx

MIT 2026 © @hoag/ui