Search…
⌃K
Links

FAQs

Anytime after you’re signed up, you can cancel by going to the Account Settings page and cancel in the Subscription tab.
If you do not cancel before your free trial period ends, you will be invoiced for your subscription.
You do. Export it, share it, deploy it as you want.
Quest generates clean code to the latest standards. You can then deploy it to your security standards and specifications.
There is no download limit. You can export your code as often as you want.
Yes, any code you’ve created is yours forever. Be sure to have downloaded the code for all of your components before you cancel your account.
Yes, you are not required to use MUI at all if you product doesn't need it.
We highly recommend using it for things like forms and buttons, etc. But if you don't need it, that is up to you. Many customers use custom components for everything they do. Also, if you have your own design system and components, you can also intergrate that with Quest as well copying and pasting placeholder components you can replace with your own components later.
Not currently but it is in our roadmap.
Not currently but it is in our roadmap.
We do not support Prototyping features at the moment. We plan to include animations that will be triggered in Quest as a feature.
This feature is not available if your component is using Breakpoints. Also, if you already used any Animate Elements feature, the option for Animate State will no longer be available as you cannot use both animations types in the same component.
Yes, by using Auto layout you can easily set how a component should behave relative to the parent or browser’s size. If you want to create different layouts or looks for different device screen sizes, you can simply create a variant for that and then use bindings to display which variant version you want for which screen size you need it for.
We currently only export and support React. We plan to support others in the near future.
Yes, you can nest unlimited amount of components inside your designs. For instance, if you have a Main component in Figma that is your custom component you want to make a React component but inside that Figma component you have an instance of another component, you can import that into Quest and Quest will see the link to that component instance and treat it as such.
You are not required to import components in any order. You can import that parent first then the child or vice versa. The link to the component instance will exist even if the component is not yet in Quest.
V17.0.0 and above. Alll features are also built to be backwards compatible.
We build everything to be backwards compatible.
Quest.ai makes iterations on the fly, meaning as soon as your designers make a change in Figma, it can be automatically updated on the code, without the developer’s intervention.
We have a single custom hook for each component where you can add the business logic.
You would need to install the redux and set it up but you connect to redux state through the hook file we generate for you using “react-redux” hooks.
Anyone can add aria labels, semantic tags and alt tags bindings from inside Quest.