Uncover {React} component usage across
your dev teams

Analyze how and where components are used across your code repos to reduce front-end tech debt and prove design system value.

>_ Have your component report ready in less than 5 minutes *

Let’s set up Omlet — usually takes less than 5 minutes

Navigate to the repo that contains your component library

Run Omlet CLI

npx @omlet/cli init

yarn @omlet/cli init

pnpm exec @omlet/cli init

Check your Omlet dashboard after following the instructions

Learn how customers use Omlet

Read the blog

Having built a similar tool in the past in order to prove a design system’s worth to stakeholders, I’m happy I can simply use Omlet now and spend more time building components instead.

Andre Luiz Rabello

Senior Frontend Engineer
Before Omlet, we had almost no insight into where and how our design system components were being used. Now, we can quickly identify underutilized or problematic components, and make rapid improvements to our design system exactly where it’s needed most.

Daron Adkins

Staff Software Engineer, UI Platforms
When I tried Omlet, it was magical. I had a dashboard in a couple of minutes with everything being tracked and visualized.

Dan Mall

Founder

>_ With Omlet you can

Understand and access more of what's happening in your code repo, like…

Measure design system adoption over time across products

Estimate the impact of deprecating a component

Identify which projects are using legacy components

Spot unused props that might cause problems later

Surface similar components to update or consolidate

Discover which non-design system components devs use most often

see Omlet in action with Proton's open-source design system

Try our demo environment

Hop into Omlet's demo environment which is pre-populated with charts and data you can play around with!

Explore example scan results

>_ With Omlet you get

Data to inform your dev roadmap, without having to scan thousands of components yourself. That gives you:

Insights into developer activity like what they're creating, reusing, or neglecting across your repos.

A view of dependencies so you can refine code without causing bugs and predict the impact of updates.

Shareable reports for stakeholders to show reduced legacy code and design system adoption.

and more

See more use cases

There are more to cover!

Discover now

Migrating Design Systems and Libraries
Increase Design System Adoption
Reducing Tech Debt
Improving Your Component Library

From the creators of Zeplin

Omlet is built by the crew behind Zeplin, a product that millions of designers and developers use. We felt the pain of managing components to ship products ourselves and have tackled the problem of design system adoption together with our users.