This was my experience as well. I felt like I was spending a lot of time learning how to code rather than thinking about the design itself. Framer Classic didn't have this problem as much because the app was self contained and the documentation was great. I also felt like Coffee Script was more forgiving.

At the end of the day, if I'm going to spend a lot of time learning JavaScript and React, I'd rather spend that time learning Swift and native development. I'm not that interested in web front-ends.

Hopefully Framer can create better guides for building components, and have in-depth documentation. Playgrounds seems like a good step towards self-contained design files. And the steps towards creating non-code based prototype interactions for simple stuff is a promising.

I do hope that you value your time and work :(

Eh no thanks. I've got an iPad Pro for that.

I do wonder if there's some way to salvage it by adding it as a new element to the keyboard rather than replacing the function row. Then it wouldn't need to do quite so much and could be more useful to the app that's in focus.

As you can see in the picture above, there's plenty of space above the keyboard. And it would be totally fine for an external keyboard to have both rows.

Glad to see some new prototyping improvements. It's going to be a long road to catch up with other prototyping tools out there.

Also, that's quite a lot of bugs fixed. It would be interesting to see which versions of Sketch shipped with these bugs to see if more bugs are being shipped versus squashed over time.

Really interested in pulling together the design and code sides of Framer into the same place. Lots of interesting ideas there.

My stack:

• Sketch
• Framer
• Invision - Would rather be using Zeplin
• Box - Would rather be using Dropbox

Some tools I'm interested in using:

• Wake
• Overflow

There are far too many Thomases in this thread.

No problem! Thanks for taking the feedback. Also one more request that's in the usability category - being able to collapse child layers into a parent layer in the layer hierarchy list. That list gets pretty long with a complicated document.

1. Multiple fills with independent blending
2. Fills for text layers
3. Blending at layer level (Color burn was what I needed)

Two other requests that are top of mind - (1) better support for adding effects to SVGs (one issue is that fills apply to the SVG bounding box, rather than the shape itself) and (2) letting shapes have sub-pixel dimensions.

Not sure if these are things other users run into, but I definitely run into the sub-pixel thing quite a bit, especially for shadows and dividers.