I did not. But I can do that in a bit. I really believe it is a calibration issue. I'll chime back when I've tested his color.

I just tried this on my Pixelbook, and I don't see the issue at all. I created a square, and applied a similar green. I exported the square as a png, and then imported the image back into Figma. Last, I created two squares, and used the color picker to pick from the image and the initial square. Both had the same hex value. I imagine this is a simple color profile issue. I had similar issues in Sketch on my MacBook Pro when I used Sketch more.

Key word....buy. I want to buy a license. Anyway. You can simply not agree with me. And that is fine. But I don't agree with a pure subscription model. Framer does it properly.

I realize that. But then why am I paying for a subscription?

All I want is to not pay a subscription. That's the main reason I don't use Adobe products. I don't always want to upgrade. Sometimes I want to decide if I go with the new version.

Why?

• Things break or change between versions that I don't want to step into because of a current project.
• I want to own my software. If I want to not upgrade to the next three versions. I want to make that choice.
• I want to vote with my wallet. If an update doesn't contain relevant features then Adobe needs to know that from the users by them not upgrading. Now they can put whatever they want in yearly updates, and we can't vote with our wallets.

I moved on from Adobe. If they brought back a yearly purchasing model I'd be in. Keep the subscription for those that want it, but allow me to buy.

My guess is that it's code based, and can be radically altered by editing the code.

A bit dramatic? Realistically any new tool my team uses has to really be worth the transition. We switched from Sketch to Figma, and the time / effort required to do these moves limits us moving to different tools merely for funsies. I'm not itching to have Framer X launched...because it's not necessary for me to use it. Our team uses lots of custom built React components with all sorts of dependencies (only work with our Microservices, requires access to APIs, web services layers, etc.) which I'd bet simply won't work in Framer X.

Yeah. I recall that being there last year. Until something is announced it's not real. It's odd that Framer isn't interested in developing for the platform. Since Windows has JavaScript as a native language (with UWP), and Microsoft even has a Design toolkit for Framer: https://docs.microsoft.com/en-us/windows/uwp/design/downloads/?ocid=cxfluent-v1June-designtoolkits-devdocs

Again. Still want to know if Windows support is being considered. Cross-platform support is necessary for us. It's why we use Figma.

That's an interesting thought, but the fact is that generationally they are using them. And with time that generation will be in the workforce. Will they graduate to Windows or Mac OS? Or will they adapt the tools they grew up with?