You should install Wikiwand chrome extension and see the magic it does.

Very vibrant... Join Join Join...

Here is a counter article answering certain aspects of John Maeda thoughts: https://blog.prototypr.io/dear-john-maeda-youre-wrong-f4d6dc024c5d

It seems that the term advanced is pretty subjective. Framer X is a prototyping tool, yes, so is Sketch, Invision Studio, XD and Figma. But X has the potential to cross the barrier from design to development or vice versa. Not promoting X here but just conveying what I have seen in the beta I received.

For some advance is the motion animation that certain tools provide but those just remain in a room full of stakeholders. For others advanced is being able to prototype with real data and interaction, those interactions can be as simple as an input field.

What most designers would expect is the ease with which custom components can be built which can be taken to production environments. Currently X can be utilised to its fullest only if you know react. Somewhere this discouraged me where I concluded its as good as Sketch or Figma but on brighter side it encourages me to learn react and hope they reduce this step size to minimum.

I have seen all of their videos as beta user which they plan to release in phases through email campaigning. The tool is so promising that I rewatch these videos to see if I have missed anything earlier and look forward to see new additions.

Yes, I have taken the course. To give you an insight before you decide on buying it.

A quick guide on starting with your own website built on react. Covers mostly aspects of css and animations before you actually dive in on react. No theoretical understanding, learn as you build. Then explore more by your own. Most important you'll be paying for the all the tutorials that Design + Code has created till date and not just the react courses. Lot of resources that come along with it. Very basic.

We use Abstract. We have tried Plant once but found it annoying when you need to clear conflicts. Abstract on the other end was very much like GIT. Its great for multiple designers collaborating on single file. Our workflow for using Abstract is as follows: 1. We commit changes at the end of the day. 2. We have artboards with names like In-Progress, On Hold and Approved. All designs have copies under each artboards. 3. Once designs are approved we remove them from the In-Progress part. 4. After every Approved page / design we merge. 5. Merging and Pulling is based on roles. Master always updates the merged files and never merges. Master only merges once the designs are in production. 6. A back up copy is kept on local drive after the merge.

Scott turned out to be a White Walker's dragon, really toned down the heat on Studio. Even if you are not a EA Studio member you can still provide feature requests to invision through twitter. They really take genuine features ahead to their dev team.