zlacker

[return to "Making Figma better for developers with Dev Mode"]
1. pcurve+um[view] [source] 2023-06-21 18:10:01
>>emilsj+(OP)
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 developers than engineers at most organizations, and this is really going to hurt the licensing cost. Definitely Adobe bean counters flexing its muscle.

◧◩
2. jozzy-+rt[view] [source] 2023-06-21 18:39:18
>>pcurve+um
> I do wonder how non-technical designers are going to feel. The learning curve is definitely going higher.

how would this impact them? just use figma as usual i would assume

looking forward to giving this a spin, our design team tends to go the iterative artboard style with everything...so sussing out values can be a pain

◧◩◪
3. pcurve+kC[view] [source] 2023-06-21 19:22:13
>>jozzy-+rt
"how would this impact them? just use figma as usual i would assume"

Since designers share files, whether at the same time, or at later date, if you have someone on the team who is fully taking advantage of all the features, like the new variables, conditional logics, etc.., and you're not quite up to speed, you may not be able to do your job effectively or may mess up what others have done.

Understanding abstractions / reference / inheritance is a skill that developers take for granted. But for non-technical folks, it takes time. Many struggle for a very long time.

◧◩◪◨
4. butler+jj1[view] [source] 2023-06-21 22:47:19
>>pcurve+kC
Designing a user interface of all things is a technical job, and non-technical folks who are asked to do that should probably study those things to do their jobs well.
[go to top]