It can't hurt to learn..

Performance is pretty choppy though.

Oh, I totally get that. My goal when designing has always been to make sure it's clear what the intention is. I was just kinda wondering if removing something because we understand people don't read is the right way to look at it.

It's free, for now.

I haven't been able to figure out how to use auto-tracing and have been messing with the app for a couple days. What am I missing?

Good points in the article but my only problem is with this statement:

"It’s well known that users don’t read instructions, and they are particularly less likely to read instructions at the top of a form. Form fields seem self-sufficient — after all, each field has a specific instruction — its label, why would you need to read anything else to fill it in?"

Should we not question why users don't read instructions? I am not saying we should put instruction in place of something that does not need explanation but I am not sure if by acknowledging people don't read we are solving what the actual problem might be?

What specifically do you think is lacking in their website?

You can also try out https://eagle.cool

Not to mention the fact that when they first introduced ember they were asking for $49.99 dollars and their reason for justifying that was that they will continuously support it with updates.

Reality has been different.

There was a time where we did wireframes using Illustrator (around version CS4) at the company I use to work for.

I remember when they added artboard support it was great. We would basically keep similar states in the same file but divide different pages types into their own file.