The post by Koen to the FB group says a whole lot more compared to the website. It all sounds pretty good, excited to see what the Framer team has come up with.

‘’’Hey Framer friends. For the last half year, we’ve been building a new product: Framer X. I’m happy to announce it today and that we’ll work as hard as we can to get it into your hands soon.

The original goal of Framer was to help people express interactive ideas. Over the years we built Framer into a full-fledged design tool that supports the whole design process, but our tool also became two products in one. We’re going to fix this with a giant leap forward.

Framer X will be more advanced than ever, using components to build entire interactive design systems based on React and ES6.

Yet, it will be easier than ever for everyone to perform common design tasks like producing graphics, expressing responsive layouts, building flows, and setting up advanced scrolling. Plus a whole lot more.

At Framer we’ve always believed that direct manipulation (canvas) and code could be mixed in a way to better express ideas. But we also want everyone to be able to use Framer and build on each other’s work. Framer X will get us very close to this and we can’t wait to show you how.

We’re incredibly excited to announce that this fall we’ll be releasing Framer X, a game-changing new product that seamlessly blends design and development. Want early access? Join our waitlist to find out what’s in store.

I don't think the objective of Framer X is to output code. When they say "React, meet design", what I take that to mean is that the API is transitioning to one or many React Component(s) instead of plain Javascript classes. Meaning: When you use design tools to insert a rectangle onto an artboard, that Rectangle is a React.Component under the hood, perhaps passing all of the design-related attributes like width, height, x-pos, y-pos, etc — as props. They can also extend React.Component and potentially add methods for managing states/transitions that will better encapsulate certain sets of interactivity that we as designers would like to model. This also bodes well for reusability of components that we author.

Original Framer + Coffeescript requires a mostly imperative approach to the programming aspect of it. A key strength of React is that it is declarative, and each component's view reacts to changes in its props. Its difficult to appreciate how powerful this difference is until you've worked with both, but I can definitely see the potential in moving Framer to a React based API, and I'm very interested to see how they did it.

it's interesting as someone who knows nothing about Framer it appeared to me entirely as a new product not an iteration of an existing one. Did the people who designed the page presume that I either know what framer 1 is or that it even exists? There is a link to framer at the top but I missed it.