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.
Get component usage insights as you’re coding
Omlet for VS Code provides insights into your component library, showing where and how components (and their props) are used right inside your editor.
Build your design system adoption dashboard
Omlet Dashboard tracks design system adoption across all your projects, helping you spot gaps where adoption is lagging and drive meaningful improvements.
npx @omlet/cli init
Learn how customers use Omlet
See how our users use Omlet to build a world class user experience.
-
Daron AdkinsStaff Software Engineer, UI PlatformsBefore 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.
- Dan MallFounder
When I tried Omlet, it was magical. I had a dashboard in a couple of minutes with everything being tracked and visualized.
- Andre Luiz RabelloSenior Frontend Engineer
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.
>_ 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
Try dashboard demo
Hop into Omlet's dashboard demo which is pre‑populated with charts and data you can play around with!
See Omlet for VS Code in action
Curious about Omlet for VS Code? Watch our co-founder Berk’s demo to see it in action.
>_ 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.
- 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.
Does Omlet support my stack?
Omlet now supports React and React Native
— Angular, Vue.js coming soon
Handy links
Next steps? All clear!
