Live data from Hacker News

Making Figma better for developers with Dev Mode

figma.com

71–80 of 238 posts

Re: Making Figma better for developers with Dev Mode

#71
post #15

Interesting, looks promising. I wonder what the status of the Adobe-Figma merger is. Personally, I hope it gets blocked to avoid more dominancy of Adobe

DOJ is planning to sue, but who knows.

UK antitrust regulator is looking at the merger as well. (the same people that blocked activision microsoft deal in UK)

https://assets.publishing.service.gov.uk/media/64523aa4faf4a...

Re: Making Figma better for developers with Dev Mode

#73
post #42

I ran a design team, and many really struggled with Sketch -> Figma transition, and took a long time. I welcome many of the new features. It's great for designers who are more technically oriented, though enterable input fields would be nice. I do wonder how non-technical designers are going to feel. The learning curve is definitely going higher. I'm worried about the rather pricey per / seat cost. There are far more…

> though enterable input fields would be nice. So funny you say this. I could actually not believe that you really need to use another tool like protopie on top of figma if you need that simple functionality eg. for a mock-up.

Re: Making Figma better for developers with Dev Mode

#74

Seems interesting, and admittedly I might have missed this, but grabbing icons as individual SVGs is probably what takes me the longest when going from design to code. I have to click on each asset, name it properly, and then export it. Over, and over again. All from different layers, and pages. If there was some sort of asset export that obeyed some spec on how to size and file name that’d save hours and hours of wo…

Right Click the icon > Copy/Paste as > Copy as SVG We use that and just paste it into the codebase. I've also used a bulk export plugin that autonames things. Would have to lookup the plugin name if you're interested.

Or even better, cmd + /, type “svg”, press enter, done

Re: Making Figma better for developers with Dev Mode

#75

Seems interesting, and admittedly I might have missed this, but grabbing icons as individual SVGs is probably what takes me the longest when going from design to code. I have to click on each asset, name it properly, and then export it. Over, and over again. All from different layers, and pages. If there was some sort of asset export that obeyed some spec on how to size and file name that’d save hours and hours of wo…

As a designer, all my icons are symbols and you can find the symbol artboard on another page with all the icons sized consistently with consistent naming conventions. You can select all and export as you please. Nothing drives me crazier than icons that are not properly formatted in both size and name.

Re: Making Figma better for developers with Dev Mode

#76

Hey all! Emil here from the Figma team that brought you Dev Mode and Figma for VS Code today! Really interested to hear what you think and also here to answer your questions. We are super excited to invest more into developers in the future, today is just the start of that!

Is there some way to export Figma's local variables to a CSS custom properties?

Re: Making Figma better for developers with Dev Mode

#77

Hey all! Emil here from the Figma team that brought you Dev Mode and Figma for VS Code today! Really interested to hear what you think and also here to answer your questions. We are super excited to invest more into developers in the future, today is just the start of that!

Hi Emil. My question is about the prototyping. The proto tooling is improving but still pretty limited. Right now the approach seems somewhat disjointed, meaning some interactions utilize variants for state change, while others work across frames with the "onclick" interaction. But that could get really messy as this grows. Question: have you considered using a "dynamic panel" approach similar to what Axure does? That model was my favorite among the proto leaders.

Re: Making Figma better for developers with Dev Mode

#78

Seems interesting, and admittedly I might have missed this, but grabbing icons as individual SVGs is probably what takes me the longest when going from design to code. I have to click on each asset, name it properly, and then export it. Over, and over again. All from different layers, and pages. If there was some sort of asset export that obeyed some spec on how to size and file name that’d save hours and hours of wo…

Right Click the icon > Copy/Paste as > Copy as SVG We use that and just paste it into the codebase. I've also used a bulk export plugin that autonames things. Would have to lookup the plugin name if you're interested.

Hero!

Re: Making Figma better for developers with Dev Mode

#79

Hey all! Emil here from the Figma team that brought you Dev Mode and Figma for VS Code today! Really interested to hear what you think and also here to answer your questions. We are super excited to invest more into developers in the future, today is just the start of that!

Does figma have an external bug tracker. While developing a figma plugin I ran into a CSP issue for loading UI web workers as blobs. Not sure if I should go through standard figma support channels or is there a dedicated channel for plugin developers.

Re: Making Figma better for developers with Dev Mode

#80
post #42

I ran a design team, and many really struggled with Sketch -> Figma transition, and took a long time. I welcome many of the new features. It's great for designers who are more technically oriented, though enterable input fields would be nice. I do wonder how non-technical designers are going to feel. The learning curve is definitely going higher. I'm worried about the rather pricey per / seat cost. There are far more…

I doubt it's adobe flexing its muscle, afaik, the DOJ is still looking into the Adobe/Figma merger. Currently Figma and Adobe are operating independently.

One under-appreciated effect of the announcement last year has been the attention and resources that have been directed toward Figma's upstart, open-source competitor Penpot. I tried Penpot back in the fall, and while it was impressive for an open-source tool, I definitely didn't see it challenging Figma anytime soon.

Fast-forward nine months, and Penpot has a boatload of new features as well as its own conference coming up in a few days. I tried it again recently, and it had come much further than I expected: not only have they implemented auto-layout (Figma's original killer feature, in my view), but with the added benefit of wrapping auto-layouts. They even announced a new roadmap item of grid auto-layout.

I loaded up a tutorial file and my enthusiasm was dampened a bit seeing how a complex document impacted performance – Penpot still has a long ways to go to match Figma there – but as a viable Figma competitor, I think Penpot might actually have a chance now. It's telling that even as Figma races ahead with this new release, there is one feature (auto-layout wrap) that Penpot got to first.

The funny thing would be if Penpot's rise, spurred by the threat of Adobe dominance, actually results in regulators giving Adobe the green light to complete its acquisition of Figma. Still, if this market becomes a healthy competition like Blender / Maya, everyone will win.

Post reply on HN