great. it has a VScode plugin, and exporting to CSS or swiftUI. that's all anyone will ever need. definitely worth fully buying into. im sure this will stand the test of time
btw this is sarcasm
Making Figma better for developers with Dev Mode
231–238 of 238 posts
Re: Making Figma better for developers with Dev Mode
#232Earlier quoted context omitted.
I've completely reneged on linking to figma in individual tasks. I take screenshots of the state of figma at the time we all agreed that "this is it" (or close enough to what we'll implement). Sure I'll leave a link in the epic to the figma "bulletin board" for that feature so that people can find it and look around. But that's it. We're also never gonna implement exactly what's shown in figma (or said screenshots) e…
At a previous job me and my team (UX Design) were so well meshed with the developers that I could hand them a text outline of the page structure I wanted of our design system components and they could produce it with 90% accuracy. Afterwards I would sit with them at their desk and we’d work out the last 10% together - either things I hadn’t thought of or bits they weren’t sure how to implement. It was glorious and it…
This is the ideal workflow that I would like to strive towards.
Unfortunately, the product designers don't seem to want to let go of Figma. I understand that this helps them think and organise the layout so perhaps it's not really a problem.
Re: Making Figma better for developers with Dev Mode
#233Earlier quoted context omitted.
That sounds like an opportunity to improve on collaboration (i.e. people talking, notifying each other) as well as trust ("compare with the figma board and flogg you because it looks nothing like it") For instance, if something is agreed upon and a designer changes it afterwards, they could simply give you a heads up that they intend to do so with context so the two of you can discuss. People > process.
They could. They don't. It may not even be their fault. They don't know. They just change things. They live in their world. You tell them, they are sympathetic, apologize, vow to do better next time. They're in their world. They do it again. The flogging still happens. Is that broken? Yes! Does it still happen in too many companies? Yes! Is there an easy fix where you "trust but verify"? Yes! (as in, sure I trust the…
> They live in their world.
That's why I really like working in true cross-functional teams. A Product Manager, a Product Designer and a handful of engineers. Do standups and all ceremonies together.
Ideally this "product team" is also empowered to solve a problem instead of tasked to build a feature.
Re: Making Figma better for developers with Dev Mode
#234Earlier quoted context omitted.
As a MacOS user with a Logitech Ergo mouse, I haven't figured out how to navigate at all, and have to get my external trackpad out just to move around. If anyone knows how to move around Figma with a scroll wheel, please tell me, seriously. I would be glad to be wrong. That said, the touchpad experience is at least intuitive.
I use this hack to turn mouse movements into scroll movements with Hammerspoon. It's one of the first things I need on a fresh install of MacOS. https://github.com/reinier/dotfiles/blob/main/hammerspoon/er... It let's you hold down the right click key and use your mouse to scroll any x/y direction. Original source for this hack is offline, but Internet Archive to the rescue: https://web.archive.org/web/20200808000102…
I am a big Hammerspoon fan, and I will definitely try this today! Thank you so much!
Re: Making Figma better for developers with Dev Mode
#235Earlier quoted context omitted.
We use figma quite extensively as a reference for our current project. The disgners constantly move stuff around, so the links to them, in tasks, break and point to nothing. Which is a major pain in the ass indeed. So yeah, 100% agree that the "big bulletin approach" is a negative.
My designers take their own snapshot by cloning their work and using versions in the names of things. Older things are not to be modified with few exceptions. It makes for a good linking experience on my end, but I don't know what that kind of maintenance is like for them.
This is my method, especially because it shows how design will progress, with tight deadlines this becomes harder but I still consider it a very valuable way of proving work (only a minor designer though with freelancing)
I certainly can understand stand the move fast method of quickly changing things, when I'm doing concept work this makes more sense here.
Long term though, if you actually care about your work you should be making copies or different boards to show how and when you made some decisions. Especially mayor design changes.(Granted I could just be a bad designer that just can't come up with a better workflow)
Re: Making Figma better for developers with Dev Mode
#236Now I need to switch between design and dev mode to get all the information I need. Typography style name is accessible in Design mode only, and margins are visible in dev mode only
Re: Making Figma better for developers with Dev Mode
#237Earlier quoted context omitted.
At a previous job me and my team (UX Design) were so well meshed with the developers that I could hand them a text outline of the page structure I wanted of our design system components and they could produce it with 90% accuracy. Afterwards I would sit with them at their desk and we’d work out the last 10% together - either things I hadn’t thought of or bits they weren’t sure how to implement. It was glorious and it…
This is the ideal workflow that I would like to strive towards. Unfortunately, the product designers don't seem to want to let go of Figma. I understand that this helps them think and organise the layout so perhaps it's not really a problem.
Figma and Sketch are fine and necessary for design tasks. We still need to quickly conceptualize and iterate on design ideas, including creating comps for research purposes.
The missing link, often, is then formalizing the design in some form that both developers and designers can use.
At the job I mentioned in my anecdote, we had a guy who lead our design system team. He had string design experience and was also a front end developer. He acted as the interface between the dec Org and the design team to create and develop a component library that was actually used in production and documented on an internal site.
Devs had real code they could use and design could focus on future products and reducing existing things.
Re: Making Figma better for developers with Dev Mode
#238Earlier quoted context omitted.
I use this hack to turn mouse movements into scroll movements with Hammerspoon. It's one of the first things I need on a fresh install of MacOS. https://github.com/reinier/dotfiles/blob/main/hammerspoon/er... It let's you hold down the right click key and use your mouse to scroll any x/y direction. Original source for this hack is offline, but Internet Archive to the rescue: https://web.archive.org/web/20200808000102…
I am a big Hammerspoon fan, and I will definitely try this today! Thank you so much!
Did it work for you?