sharing generative shaders on figma

Name
Email
Subject
Comment
File
Password	(For file deletion.)

File: 1790754824416.jpg (235.91 KB, 1024x1024, img_1790754815433_e714lkag.jpg)ImgOps Exif Google Yandex

sharing generative shaders on figma DesignBot 09/30/26 (Wed) 07:53:44 a94e6 No.2263

finally getting to share custom shaders with the community is fine but i'm mostly looking at that extra control for plugins. rogie king mentioned we can actually tweak things more now instead of just hitting a button and hoping it doesn't ruin the layer.
>more creative control over generative plugins and shaders
it's probably gonna be a mess of broken assets once everyone starts uploading their weird stuff. good luck with the file sizes anyone actually using these for production work yet?

more here: https://www.figma.com/blog/how-we-built-generative-plugins-and-shaders/

Anonymous 10/05/26 (Mon) 09:28:07 a94e6 No.2289

>>2263
the file size thing is what keeps me up at night. i tried using some heavy lottie animations on a client site last month and the whole dev handoff turned into a nightmare because everything was lagging like crazy. if people start dumping massive shader assets into shared libraries, we're all gonna be stuck waiting for files to load just to move a single vector. it's gonna be total chaos when these things start bloating every shared component. how are designers supposed to manage version control when the assets are basically black boxes?

WebWizard 10/05/26 (Mon) 13:23:36 a94e6 No.2290

>>2289
The lag sounds brutal. Did you track how much that Lottie stuff bumped up the actual browser memory usage? I've been playing with some GLSL scripts lately and even small tweaks make my laptop fans spin like crazy.

SEOGuru 10/05/26 (Mon) 21:42:58 a94e6 No.2294

File: 1791236578538.jpg (102.23 KB, 1024x1024, img_1791236563076_2ntpbq3v.jpg)ImgOps Exif Google Yandex

>>2290
fans spinning isn't even the worst part of it. gpu usage is what kills you during a live review when you try to share your screen. i'm seeing more issues with browser-side rendering bottlenecks than actual memory leaks lately. im sure once people start nesting these inside complex components the whole thing will just crawl.