Your current individual Framer subscription will be valid for Framer X too so you can buy a subscription today, but you will still have to be invited. People with a subscription do get it before anyone else.
We are currently working on Framer X for Windows, but it is decoupled from the beta so we can get it in your hands as fast as possible. Sign up here and we'll keep you updated.
To maintain stability and offer a great experience we are rolling out our Beta access in batches and are ramping up the batches day by day. If you are subscribed to Beta Access list then your invite will follow soon.
Yes, even better. But the current beta does not include all functionality yet because we're still working on some code features. They will land in the next beta versions.
We aim to support both TypeScript and plain ES6 on release.
The point of Framer X is not to generate code for you but use the code you (or someone else) wrote to compose interfaces. We do however aim to be able to let you import design components from any arbitrary React project on release.
We're still working on the private store. If you'd like to test early, contact our enterprise team via the form on the Framer X site.
You can, we just use
React.Component in the docs not to confuse beginners by mixing the two. If you are a beginner who is now curious read this.
However you like. We prefer inline styles, but everything from Styled Components to Glamour should work.
package.json that temporarily get extracted while your project is open. You can reveal the contents with
File > Show Package.
This is still very fragile but you can open a Framer X project,
File > Show Package and use the terminal to use
yarn add <package> .
Any Framer store package lives under the
@framer namespace. Every other package name will be proxied through to public npm.
You can currently only access
props.children but we're working on better ways to mix code and canvas.
Right now, packages are binary zipped files and not great for Git. We're looking to improve that in the future and we think we can, because Git is smart.
We will keep supporting and updating Framer Studio once we release Framer X so that you can continue to open and edit all your previous projects, but our main focus will shift towards Framer X.
Some might work for the design side only, but this is very buggy. It's better to create a new project and copy over all your Frames.
Framer has created the "Syntax Theme": awesome looking themes for both Visual Studio Code and Atom, so that you can code your components in true Framer style.