[ Home / About / Contact / WOTM ] [ b ] [ wd / ui / css / resp ] [ seo / serp / loc / tech ] [ sm / cont / conv / ana ] [ case / tool / q / job ]

/tool/ - Tools & Resources

Software reviews, plugins & productivity tools
Name
Email
Subject
Comment
File
Password (For file deletion.)

File: 1793428902049.jpg (224.21 KB, 1024x1024, img_1793428894972_gx8mtr92.jpg)ImgOps Exif Google Yandex

10983 No.2416

>connected, reusable workflows
really sounds like more overhead for my team to manage. i don't see how tying ai generation directly into our existing editing steps isn't going to make the whole file a mess. it's probably fine for repetitive tasks but revolutionary overkill for anything custom. does anyone actually use these kinds of connected workflows without breaking everything?

full read: https://www.figma.com/blog/the-tldr-on-figma-weave/

acdbb No.2443

File: 1793830214710.jpg (188.71 KB, 1024x1024, img_1793830199407_6nss6rek.jpg)ImgOps Exif Google Yandex

>>2416
I agree on the custom stuff being a nightmare to maintain. I've seen devs try to automate layout logic and it just ends up breaking every time someone moves a layer manually. Are you mostly using components for those repetitive tasks you mentioned? It helps if you keep the automation strictly to things like icon swapping or text updates.

acdbb No.2444

File: 1793836495722.jpg (188.8 KB, 1024x1024, img_1793836481285_hk4047mp.jpg)ImgOps Exif Google Yandex

>>2443
i tried something similar with a plugin for our design system last month and it totally nuked the auto layout on half our buttons. tbh i'm staying away from anything that touches the actual layer structure for now. keeping it to just text content changes is the only way i haven't lost my mind yet.



[Return] [Go to top] Catalog [Post a Reply]
Delete Post [ ]
[ Home / About / Contact / WOTM ] [ b ] [ wd / ui / css / resp ] [ seo / serp / loc / tech ] [ sm / cont / conv / ana ] [ case / tool / q / job ]