5 ms·
Show HN: Mirrorful – A developer-first way to implement designs faster
Hey HN! Mirrorful (https://www.mirrorful.com/ https://www.mirrorful.com/) is an open-source developer framework that helps front-end engineers manage their design systems. We’ve been building Mirrorful with the open-source community (https://github.com/Mirrorful/mirrorful https://github.com/Mirrorful/mirrorful) and wanted to share our beta with you. Check out our online demo to get the idea: https://app.mirrorful.com/ https://app.mirrorful.com/.
Design systems can be thought of as the “building blocks of your app” which makes me think of Lego bricks. Mirrorful helps you manage your codebase’s Lego bricks and ensure that they are consistent across all of your apps and platforms.
We saw as product engineers how hard it is to get code to match Figma mock ups. High-quality design is a competitive advantage, so getting your UI pixel perfect can matter a lot, but is time-consuming and tedious.
When we worked for large public companies, we saw that good component libraries help, but engineers are often still dealing with tweaking small design decisions. There are a lot of inefficiencies. We also worked at a small startup and saw what it was like to not have a design system. No design system led to copy pasta code, and days of back-and-forth on simple things like “what hex should i be using for the hover state?”
Design systems are tricky to get right. Picking an out-of-the-box solution is easy to begin with, but one day you’ll be cursing yourself due to lack of flexibility (we did!). On the other hand, creating a design system from scratch is super time-consuming even for the best frontend engineers. Mirrorful is our way out of this dilemma.
Mirrorful is completely open-source and written in Typescript. We’re starting with basic design elements—commonly called “design tokens” — such as colors, typography, and shadows, but have plans to expand our scope into more complex components.
As frontend engineers ourselves, we wanted a tool that lives in code but is visual. It had to be super easy to set up, but also prepare you for scale so you and/or your team don’t end up copy-pasting everywhere. We decided to make it an NPM package (https://www.npmjs.com/package/mirrorful https://www.npmjs.com/package/mirrorful) that runs a localhost editor and exports out your design tokens into any configuration you want: .js, .ts, .css, .scss, .json. It’s lightweight with no design system lock-in.
Our product is completely self-serve: just install our NPM package. If you run Mirrorful locally, a visual dashboard will pop up at localhost:5050 that lets you manage your theme and export various configuration files directly into code.
Pricing is similar to other open-source companies—we charge for cloud-hosted features and for premium components.
We’ve built open-source/open-core projects before and love interacting with contributors from all over the world. If anyone has any opinions on what we’re building, we’re all ears. Check us out at mirrorful.com and at github.com/Mirrorful/mirrorful and give it a shot!
- Nijikokun 4y agoWhats the benefit of this over something like docz or storybook? Which are also agnostic to framework?
- teddarific 4y agoWe’re actually huge fans of platforms like Docz and Storybook! With Mirrorful, we want to complement these documentation-first platforms rather be a replacement (some of our initial users use both us and storybook!). We’re more focused on the actual implementation aspect of building new features, rather than serving as a reference. For example, Mirrorful helps ensure that an engineer is using the right color that the designer intended and isn’t just hard-coding colors all over the place. I think our value props are similar, in that we’re all looking to speed up engineering velocity and help with design consistency, but targeting different parts of the workflow. There’s a lot of places where things go wrong in the process today!
- joduplessis 4y agoNice work! Whilst I do love the hands-on approach of something like Style Dictionary, I can see the value prop here. Especially with design system standards semi-converging (in the wild at least). Any plans on supporting native platforms in the future (sorry if I missed it in the docs)?
- teddarific 4y agoLove your point about design system standards semi-converging, we totally agree! We think design systems is slowly transitioning from an art to a science. We do have plans on supporting native platforms! We've been holding out a little bit to see what folks specifically in mind, so if you have a thoughts or a specific platform in mind, let us know and we'll get it prioritized! Also, we have an active Slack community if you're interested in conversing more there: https://join.slack.com/t/mirrorful/shared_invite/zt-1ps2xtxh0-2NaixFfFzSKZbr5gw_AHfA https://join.slack.com/t/mirrorful/shared_invite/zt-1ps2xtxh...
- 4y ago