website of the year :)

It's a good starting point but I agree, being able to set padding per side would be awesome :)

It would be great to see YoY change for each category (where applicable) so that we can see the trends for more categories. Very nice summary though :)

States for components look interesting. Hope Figma and Sketch will steal it with pride :)

Looks more like a replacement for Principle rather than Sketch/Figma/XD. Will be interesting to see how the product evolves but for a first release it has a lot of great features. Hope they add components/symbols soon to make it easier to reuse elements.

One thing that has me a little worried is that it, just like Principle and Flinto, is focused on transitions between screens. This makes it really hard to work on multiple interactions within the same screen because you end up having 10 copies of the same screen for different interactions inside the same view. This is where apps like ProtoPie really shine. Where I would have to make multiple screens to simulate multiple states/interactions inside the same screen in Principle I can just make it all in one screen in ProtoPie and if I change something in the design I just have to update one screen instead of 10 copies of the same screens (for different states).

very interesting findings. I'm using a 13" MBP with an i7 and primarily use Figma because Sketch just grinds to a halt once the project becomes complex enough. But at the same time, my computer almost never gets hot enough for the fans to kick into high gear when using Sketch. The same can't be said about Figma where I have to live with the fan-noise throughout most of the workday. Thankfully there is such a thing as noise-canceling headphones :)

I'm interpreting this as a command line with a GUI layer. I can see the appeal of that in some cases but for the most part, it seems like it will have the same hurdles as most smart assistance. They are a bit of a black box and it's very hard to know what they can or can't do and what the correct syntax is. Having to constantly consult the "more actions" for each new application/function seems like a bit of a pain. Especially on an OS level, there are so many commands and action that you can do at any time, the list would be absolutely massive.

Another thing that is very unclear is how you would actually access files. At some point, I will have to browse my files since most applications or functions tend to generate new files (word processors produce text files, image editors create images, etc). For example, I want to send some photos to my colleague, I have to find the photos somehow and maybe they are massive RAW files so I want to zip them. How do I find and select the photos I want to send? I can sort of imagine how the zip/compress would work but where does the resulting file end up? And after it is sent, will the zip be deleted or does it just sit somewhere on the hard drive where I can't see it?

Sounds like a cool concept and I like the focus on flow and simplification. I'm looking forward to seeing what else comes out of this but as it stands right now, as with most concepts, the more you look at it the more questions it generates :)

Obligatory "any crashes? Is it safe to use?" comment

I tried importing it into Figma but found that the work file became super slow. First I thought that it was Figma that was slow but I kept hearing how fast Figma was compared to Sketch so I decided to rebuild it from scratch in Figma instead. It made a huge difference in performance for some reason. Also, you probably want to restructure your components because they work differently in Figma compared to Sketch. Figma's components are more flexible and usually require fewer components to get the job done.

That's what I used. The current library is now ~200MB (was around 400MB before compression). Still too much for my poor little MBP :(