omlet.dev Open in urlscan Pro
44.226.170.49  Public Scan

URL: https://omlet.dev/?utm_campaign=partner_this-week-in-react_newsletter-quick-link-oct-2024
Submission: On October 28 via manual from BE — Scanned from US

Form analysis 0 forms found in the DOM

Text Content

 * Docs
 * Pricing
 * Use cases
 * Blog

Try demo Login Get started
 * Docs
 * Pricing
 * Use cases
 * Blog

Try demo Login Get started


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.

Sign up Try for free Try demo Watch demo
>_ Have your component report ready in less than 5 minutes *How?
Let’s set up Omlet — usually takes less than 5 minutes
1
Navigate to the repo that contains your component library
2
Run Omlet CLI
npm yarn pnpm

npx @omlet/cli init

yarn @omlet/cli init

pnpm exec @omlet/cli init

3
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.


DOES OMLET SUPPORT MY STACK?

Omlet now supports React and React Native
— Angular, Vue.js coming soon


HANDY LINKS

Next steps? All clear!


GET STARTED FOR FREE

No credit card required

Sign up


TRY DEMO TRY DEMO ENVIRONMENT

Explore Omlet's features with live data

Try Demo Environment


WATCH DEMO

Get a glimpse of Omlet's powerful component tracking

Watch now


CONTACT US

Have questions? Our crew is here to help.

Get in touch
 * Terms
 * Privacy
 * Contact us


Close

Close