31–40 of 54 posts
God I hate software.
Figma’s dev mode was just a way to take existing functionality and gate it behind a higher price point under the guise of “new functionality”. As a developers i found it simpler to access css from figma via the old inspect vs. having to toggle in and out of dev mode. It is shady to take a commonly used feature and move it behind a higher tier after years of offering to people already giving you money. Just classic VC…
Sketch really lost because they did not want to go cross-platform..
In practice the vast majority of designers are using Mac, so it's not like it not being cross platform was the problem. The thing that made Sketch lose against Figma was that they never really tackled the issue of collaboration until Figma came along, leaving it for 3rd parties like Invision and others to solve. Now they have most of the collaboration features they were missing, but by then it was too late and Figma…
Why Figma won is, at least in my own experience, due to two areas where they roundly beat Sketch: auto-layout and performance.
Auto-layout was one of those squandered first-mover advantage stories: Sketch had it first, but built it into the symbol/component system and never envisioned it as a global feature. Figma did, and it was a total game-changer. Overnight, everything else felt like using Photoshop in comparison.
Why couldn't Sketch just generalize its own auto-layout feature? They finally did (only about three months ago!) but I suspect it had to do with Sketch's architecture, which leads into the second Figma advantage: performance.
From the start, Figma turned the native-app-versus-web-app intuition on its head. Being browser-based, it should have been much slower than Sketch... but due both to Sketch's legacy as a general-purpose vector graphics app and Figma's stellar engineering org, Figma was leagues faster when it came to the kind of big, complex files design orgs deal with on a daily basis.
Between these two things, the writing was on the wall. I hope Sketch has a chance to come back, though – missteps like Dev Mode give them an opening now that they've had several years to catch up.
Sketch really lost because they did not want to go cross-platform..
- No more file-sharing issues. Designers are not good at using tools like git. I used git+lfs to store my designs, but most of the design team used Google Drive or Dropbox. In both cases, you end up in a situation where the file you are looking at is not up-to-date. Figma removed that issue.
- Design reviews: Collaborating on the same design as in many Figma demos is rare. However, playing with the design in a remote session is common during a design review.
- The pace of updates: Figma moved faster to improve the editor's UX. The auto-layout, styles, components, and variables are good additions to everyday work. It took Sketch a while to update the editor's UX.
There is no return once the team purchases the Figma subscription instead of renewing Sketch. When I started using Figma (around 2019), I hated its slowness and missed some Sketch features. Our UX team adopted Figma, and only a few designers continued using their Sketch license (I was one of them). But, it didn't make sense to not align with the rest of the team (for the reasons mentioned before). I haven't used Sketch since then. Sketch added many sharing features, but there isn't a solid reason to go back and convince the team to migrate their designs.
Penpot is great, free, and doesn't rat** you. Oh and it's made by a kickass collective. That is where I went when I binned Figma.
Let's hope they find a sustainable business model, because the people working there needs salaries and hosting needs paying...
But I don't have the expertise to know for sure.
It sounds to me that if your team is relying that much on inspecting values, you're doing the developers (or designers) a disservice one way or another. A well defined set of design tokens is all that's needed, and isn't rocket science either. Not to mention that encouraging developers to copy-paste CSS should be frown upon anyway.
edit: there is a free tier but core functionality like "create a variable" or "reference a variable" is Pro-only :P
Earlier quoted context omitted.
Well, different market really. Afaik, Sketch is still macOS only.
Mac is required for designing, which in pratice most designers are using in the vast majority of organizations, so it's not really an issue. For feedback and handoff the web tool is free and works in any OS that has a browser. https://www.sketch.com/handoff/
Earlier quoted context omitted.
Well, different market really. Afaik, Sketch is still macOS only.
Mac is required for designing, which in pratice most designers are using in the vast majority of organizations, so it's not really an issue. For feedback and handoff the web tool is free and works in any OS that has a browser. https://www.sketch.com/handoff/
Yet it entirely lacks value.
Greater design positions don’t rely on Mac’s lol so why should more simple design?
It sounds to me that if your team is relying that much on inspecting values, you're doing the developers (or designers) a disservice one way or another. A well defined set of design tokens is all that's needed, and isn't rocket science either. Not to mention that encouraging developers to copy-paste CSS should be frown upon anyway.
And the CSS code output can also carry design tokens.