Omlet Docs
BlogChangelogAsk the CommunityContact Sales
  • Get started
    • What is Omlet?
    • CLI & Dashboard
  • Omlet for VS Code
  • CLI & Dashboard
    • CLI
      • Your first scan
      • Set up your dashbard
      • Future scans
      • Ensure data accuracy
      • Config file
        • Exports configuration
        • Mapping aliases
        • Excluding certain components & files
        • Tutorial: Config file
      • Custom component properties
        • CLI hooks
        • Tutorial 1: Team/code owner usage
        • Tutorial 2: Package version tracking
        • Other example scripts
      • Set up regular scans
      • CLI commands
        • init
        • analyze
        • login
    • Analytics
      • Popular charts
      • Create custom charts
      • Save charts to dashboard
      • Share charts and dashboards with your team
      • Download chart data
    • Components
      • Search and filter components
      • Component tags
      • Dependency Tree
      • Props tracking
    • Workspace & Account
      • Invite team members
      • Renaming projects
      • Update your email address
      • Access your billing details & invoices
  • Security
    • Security in Omlet
    • Data collection
  • Help
    • Pricing
    • FAQs
      • How detection works?
      • Monorepo support
      • How to delete scans?
      • Omlet vs. React Scanner
      • Working with multiple workspaces
    • Troubleshooting
      • Debugging CLI issues
      • Some components aren't detected
      • API failed or timeout
      • Are you behind a proxy?
      • Troubleshooting Git errors
Powered by GitBook
On this page
  • How Omlet can help?
  • Why Omlet?
  • Easy to set up, no code needed
  • Unlock the value of your design system
  • Continuous improvement and customization
  1. Get started

What is Omlet?

Learn more about Omlet—component analytics and insights for React.

NextCLI & Dashboard

Last updated 4 months ago

Omlet provides component analytics and insights for React & React Native. You can measure your production component usage to optimize your codebase and drive design system adoption.

With ready-to-use charts, you can understand how components across projects are adopted over time and use data to make informed decisions, such as which components and props to keep, remove, and improve—driving development strategies confidently.

How Omlet can help?

Omlet can help you find answers to questions such as:

  • How is my design system used over time vs. the current adoption?

  • Which team and projects are using design system components?

  • Which products are using my older components?

  • Are teams moving through versions successfully?

  • How do we update older components without affecting their dependencies?

  • What are the new components, and which ones are being used?

  • Which component props should be added, updated, or removed?

Why Omlet?

Easy to set up, no code needed

Component tracking can be challenging for development teams. Omlet eliminates manual intervention and custom engineering. Setup takes less than 5 minutes, providing quick access to valuable analytics.

Unlock the value of your design system

Omlet helps you demonstrate the value of your design system by providing usage insights to allocate development resources, improve collaboration, and showcase design system ROI.

Continuous improvement and customization

Omlet is committed to continuous improvement and customization to meet the evolving needs of development teams. We ensure you have access to insights for optimizing your design system and the flexibility to tailor Omlet to your specific requirements.

If you'd like to learn more about Omlet or have questions, feel free to contact us at .

support@omlet.dev