Searchโ€ฆ
Easily Sync Designs without Losing Work
When you first export a component from Figma to Quest using the plugin, you'll be taken to the Quest Editor where you can start to add features, props, state triggers and bindings.
Sync Component any time after you first export it
One of the biggest benefits of using Quest is we do our best to compliment your workflow instead of a being a simple tool to convert designs to code (like our competitors). What this means for designers is you can continue to work and update designs and Sync back to Quest without asking developers to redo their work. Once you export your design to Quest, you can easily make edits to it and then Sync it back to Quest without fear of breaking anything.
Quest uses the internal GUID that Figma provides for each layer that is extracted. When you add a feature or binding to that layer in Quest, we always remember the link to that layer. This makes it easy to continue to iterate on your design without the fear or losing that set up in Quest.
You can update the following without fear of breaking features or bindings in Quest:
  • Layer names
  • Layer orders
  • Layer properties such as font, text, color, fills, roundness, etc.
For instance, if you already exported a component, and you want to add a new text field and button, you do that in Figma, use Quest plugin to "Sync Component" and then in Quest, you set up props/bindings for the new text and button, then export the Component or export the App. Once exported, replace the component file BUT don't replace the logic file you already have logic in, just add the additional parts you added to the original file. So if component were called "Card" you'd export it and replace the "Card.js" and merge the "useCard.js" file. No need to start from scratch with a new component, just always Sync the component you're updating back to Quest.
โ€‹
Copy link