Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Why Figma Wins

kwokchain.com

Post reply on HN
Print view View original

171–180 of 191 posts

Re: Why Figma Wins

#171

Post by andratwiro »

josefrichter wrote: post #150
satvikpendem wrote: post #42

Figma approaches design from an engineer's perspective. They have features like auto layout [0], swapping elements in a list, scaling multiple elements at once while preserving each aspect ratio, and so on. Can you imagine that if designers before this wanted to move an element in a list, they would have to move every single one instead of having some drag and drop swap functionality? That if they wanted to dynamical…

Framer doesn't spit out React code once you're done. Code used in prototyping is hugely different and unusable in production. And Framer makers know this and openly talk about this, they're not trying to be a code generator.

Well, I've found it pretty useful to hand animation in js as-is for specific patterns (as we actually handle the specific bezier curve animation, timings, etc...)

Re: Why Figma Wins

#172

Post by andratwiro »

hypewatch wrote: post #9

Figma sounds like a great tool, but it feels overhyped to me - especially in this article. This reads like a long-winded pitch to a Figma investor more than an honest review. I’ve been wanting to try it out but this article was a little bit of a turn off because it is so enthusiastic. Every tool has strengths and weaknesses so an article like this makes me wonder, what are the trade offs?

Definitely, I'm not affiliated to Sketch but there are a few things on the article that are outdated. Through Sketch Cloud you can actually handle commenting, clickable prototypes and assets for the front-end team (avoiding using Zeplin and Invision). The plugin ecosystem is really strong on Sketch as well, and they are also rolling out collaborative editing this year.

Re: Why Figma Wins

#173

Post by [deleted] »

waheoo wrote: post #144
Stevvo wrote: post #141

Earlier quoted context omitted.

Agreed. In my company, your responsibility as a developer is to implement the design as shown on figma, pixel perfect. If something is incorrect on the design, someone will usually have noticed it and fixed it before I get the chance, because there are 4 sets of eyes on it (CTO, PM, Designers, Developer)

I hope this is sarcasm.

[deleted]

Re: Why Figma Wins

#174

Post by [deleted] »

cm2012 wrote: post #104
vosper wrote: post #31

We use Figma at work, and while it’s a nice tool I think it’s easy to fall (or maybe we just fell) into a kind of uncanny valley. The designs we get are close to realistic mockups of our actual UI, but are often not 100% there, and it’s the little deviations that can be quite distracting. Engineer: So are we changing the nav icons as part of this story, too? Designer: Oh, no, ignore that. I didn’t have our real icon…

Here's the thing: higher ups, more often than not, have no imagination. If your mock-up is not explicit and realistic, you'll get complaints and worries that it's not polished or that not a lot of work went into it.

[deleted]

Re: Why Figma Wins

#175

Post by [deleted] »

cmrdporcupine wrote: post #139
vosper wrote: post #31

We use Figma at work, and while it’s a nice tool I think it’s easy to fall (or maybe we just fell) into a kind of uncanny valley. The designs we get are close to realistic mockups of our actual UI, but are often not 100% there, and it’s the little deviations that can be quite distracting. Engineer: So are we changing the nav icons as part of this story, too? Designer: Oh, no, ignore that. I didn’t have our real icon…

Agreed. And I think there's a certain personality of people who are employed in UX that lean more towards the design than the conceptual side that often get lost in the weeds with this stuff, too, and you'll end up with a series of mocks that look great, smell great, and gosh darn it people like them... but are missing all error screens, corner cases, more complicated states, and leave developers in the dark on the b…

[deleted]

Re: Why Figma Wins

#176

Post by [deleted] »

OzzyB wrote: post #56
corytheboyd wrote: post #12

Not a comment about Figma really, but it has unfortunately become a trigger word for me. These are my observations from working with tech startup companies as a software engineer. Software solutions will never fix problems that are caused by people. Sketch, Figma, whatever the next design tool is. Google Docs, Quip, Notion. Trello, Pivotal Tracker, GitHub/ZenHub, Jira. I've gone through tool-switching fatigue with al…

I thought the Waterfall process was primarily an Agency/Marketing thing, with Tech Startups focusing more on a level playing field where most have input and touch the final product. This is where I believe these products are focused on, essentially agencies try to get sign-off from clients before they begin work, and the better they can show what the final product (and processes) will be like, the better. Edit: Yes t…

[deleted]

Re: Why Figma Wins

#177

Post by bshimmin »

dakiol wrote: post #170

Interesting. I have a 2017 MBP, 16GB, 2.9 GHZ quad-core, and Figma feels terribly slow.

I briefly had Figma, Zoom, and Slack (three workspaces) open at once on Friday on my Mac. My computer was more or less unusable and sounded very sorry for itself; it was sort of entertaining, baffling, and sad all at the same time.

I ended up quitting Slack and asking the designer if she could show us the Figma stuff over screenshare on Zoom instead. Obviously multi-tasking is too much to expect these days.

Re: Why Figma Wins

#178

Post by hising »

All design tools lack the ability to design the most important part of an UI: state. I think Figma is an awesome tool for making good looking mockups, but as a tool for describing how the UI will actually work, it has the same flaws as all other tools for this. Storybooks are great but there is still need for endless discussions when converting fancy Figma designs to actual interactive components with state

Re: Why Figma Wins

#179

Post by gitgud »

geoffw8 wrote: post #166
waheoo wrote: post #144

Earlier quoted context omitted.

I hope this is sarcasm.

Seems pretty reasonable to me. If it’s a rough wireframe it can be just that, rough. If it’s a pixel perfect mockup then it’s a contract for final product IMO. Of course whether there are that many sets of eyes on it depends how big a co you’re working for!

Pixel perfect? So if a css box-shadow is 11px instead of 12px someone will notice? ...I don't think so

Maybe if the pixel perfect design is diff'd against the final product...

Re: Why Figma Wins

#180

Post by wx196 »

hising wrote: post #178

All design tools lack the ability to design the most important part of an UI: state. I think Figma is an awesome tool for making good looking mockups, but as a tool for describing how the UI will actually work, it has the same flaws as all other tools for this. Storybooks are great but there is still need for endless discussions when converting fancy Figma designs to actual interactive components with state

It depends on what you call "design". User flow, interactions, states, rectangles and colors or just rectangles and colors. If first, there are a lot of other tools, maybe not so hyped so you don't see them every day. Just to name a few: Axure, Justinmind, iRise, Indigo Design. Recent version of Adobe XD is quite a powerful tool as well. With the rise of rapid application development tools we possibly can add Bubble, Retool, Outsystems and similar tools to this list too.
Post reply on HN