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.

Definitely a +1 for ES6 support. ES6 has so many of the features that made Coffeescript a great alternative to the Javascript of old. The syntax for Coffeescript has a nicer aesthetic IMO, but I would prefer to write prototype code using the same syntax I write my production application code in, as one less context switch is always a huge win. There is also so many great (and free) resources on the web for learning ES6.

Hi Ivan,

Big fan of your work. I think it is becoming increasingly clear that rethinking the role of the document has the potential to unlock a lot of value for individuals and businesses in our modern, mobile, and connected context. Salesforce's recent $750M acquisition of Quip is one significant market validation of this movement.

I have kept a close eye on this space for quite some time, and Notion has the most interesting approach that I've seen yet. There are two very large opportunities that I see in the product, and am curious how you're thinking about them.

1. Regarding collaboration: Notion is clearly promoting Slack as the tool to enable communication around the content within Notion. Part of what made Quip so powerful and valuable for me was the colocation of conversation and content. The context is so much stronger when you can hover/tap a highlighted segment, and surface the questions/commentary pertinent to that piece of content without losing your place. It made achieving a full understanding of the relative development of the document quite doable. How are you thinking about enhancing Notion's capabilities to bring rich conversation directly into the content? Maybe Slack can still serve as a remote notification center and changelog, but only as a redundancy?

2. Regarding todos and team coordination: I use the checklists in Notion and like them, but there are still questions that cannot be answered in Notion. Questions like: What is due for me by the end of the week? If I was working with a team in Notion, I might ask: What does Jay have on his plate this week? Again, I see benefit in colocating the tasks my team is accountable for with the content needed to perform those tasks, just as I do in colocating conversation and content. Combine all three in the right way, and you have something truly unique, and incredibly powerful. Is Notion of the opinion that it should be a supporting role in team productivity, maybe living life as a hyperlink in the notes section of a task in another more dedicated piece of task management software, or are you thinking about how to move todos into first class within your system?

I think you guys are the team to make this happen, I truly do. Keep up the great work.

At the end of the video announcement, they say "Invision, Craft, and Sketch... the product design platform of the future is already here".

That's a bit cheeky though, given that Motion was announced 6 months ago as "Coming Soon", and Inspect was announced 7 months ago, and has just entered into private beta.

Is anyone concerned about this, or does InVision's track record for shipping ease your mind?

Hi Chris. I'm a huge fan of your work.

Motion and interaction design are on the ascendency, which I believe is in service of making software more understandable & enjoyable to use.

Given that Sketch aims to be the go-to tool for interface designers, how does the Sketch team think about addressing motion & interaction as integral parts of the interface design process?

Hey Justin, congrats on joining Matias & team. I see that Relative Wave's Form has just been updated as well. It seems to me that Pixate & Form are really two approaches to the same problem. Did you discuss this overlap with Google and wonder at the confusion this might cause? For example, why would I choose Form over Pixate if I'm designed for iOS?