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
Explore ideas fast without detaching from the live mockups and real data — clone components in one click and keep all overrides on instances.
When done, converge iterations to a single component and apply changes across the whole system.
→ How to iterate at the speed of light using components
To summarize: at its core, Master gives you the ability to turn anything into a component instance!
Never worry about detached instances again!
Questions? Feedback? Need a demo? Let's chat: firstname.lastname@example.org
42 000+ people already used Master in their work! Are you ready to reveal its magic too?
Joel Califa — GitHub
Tom Lowry — Figma
Ridd — Figma Academy, Dive