I’m working on an app design and every time I create a new element I think to myself: “Should I make this a component?” Master allows you to not worry about this. Stay in the flow and create components only after you need them.
No more “damn, should've used components”
Compared to the native method, moving components with Master is safe and easy. Master can swap old local instances to the new library component without losing any overrides! If something goes wrong, you can undo the changes and try again.
→ Learn how to move components between files
There are several plugins that can clone components, but Master not only saves all overrides in the instances when cloning a component — its flexibility also allows you to converge your iterative process back to one component after you finalize it.
To summarize: at its core, Master gives you the ability to turn anything into a component instance!
Questions? Feedback? I’m always eager to chat: firstname.lastname@example.org
Secure Gumroad checkout
25 000+ people already used Master in their work! Are you ready to reveal its magic too?
Joel Califa — GitHub
Tom Lowry — Figma