<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Code Layers - Burak Poryaz - Web ve Mobil Arayüz Tasarımı - UX Ui Tasarım</title>
	<atom:link href="https://poryaz.com/tag/code-layers/feed/" rel="self" type="application/rss+xml" />
	<link>https://poryaz.com</link>
	<description>Mobil Arayüz Tasarımı, Mobile Ui/UX Designer, Mobile Interface Design, Web Arayüz Tasarımı, Burak Poryaz</description>
	<lastBuildDate>Wed, 24 Jun 2026 23:24:19 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=7.1</generator>

<image>
	<url>https://poryaz.com/wp-content/uploads/2023/11/cropped-favicon-1-32x32.png</url>
	<title>Code Layers - Burak Poryaz - Web ve Mobil Arayüz Tasarımı - UX Ui Tasarım</title>
	<link>https://poryaz.com</link>
	<width>32</width>
	<height>32</height>
</image> 
	<item>
		<title>Figma Config 2026: AI, Code Layers and Motion Change the Design Tool</title>
		<link>https://poryaz.com/figma-config-2026-ai-code-layers-motion/</link>
		
		<dc:creator><![CDATA[poryaz]]></dc:creator>
		<pubDate>Wed, 24 Jun 2026 23:24:19 +0000</pubDate>
				<category><![CDATA[AI]]></category>
		<category><![CDATA[Growth]]></category>
		<category><![CDATA[Product Design]]></category>
		<category><![CDATA[Technology]]></category>
		<category><![CDATA[Tools]]></category>
		<category><![CDATA[UI/UX]]></category>
		<category><![CDATA[AI Design]]></category>
		<category><![CDATA[Code Layers]]></category>
		<category><![CDATA[Design Tools]]></category>
		<category><![CDATA[Figma AI]]></category>
		<category><![CDATA[Figma Config 2026]]></category>
		<category><![CDATA[Figma Motion]]></category>
		<guid isPermaLink="false">https://poryaz.com/figma-config-2026-ai-code-layers-motion/</guid>

					<description><![CDATA[<p>Figma Config 2026 shows that Figma is becoming more than a screen design tool. AI, Code Layers, Motion, shaders, and generative plugins can change how designers work.</p>
<p>The post <a href="https://poryaz.com/figma-config-2026-ai-code-layers-motion/">Figma Config 2026: AI, Code Layers and Motion Change the Design Tool</a> first appeared on <a href="https://poryaz.com">Burak Poryaz - Web ve Mobil Arayüz Tasarımı - UX Ui Tasarım</a>.</p>]]></description>
										<content:encoded><![CDATA[<p>Figma Config 2026 feels like a clear message: Figma is not only a place to draw screens anymore.</p>
<p>It is becoming a bigger product workspace.</p>
<p>Design, code, motion, AI agents, shaders, and repeatable workflows are now getting closer inside the same canvas.</p>
<p>For UI/UX and product designers, this is important. Not because every new feature must be used tomorrow. But because the role of the designer is changing again.</p>
<h2>What Figma announced at Config 2026</h2>
<p>The main updates around Config 2026 include Figma Motion, custom shader effects and fills, Weave tools inside Figma Design, updates to the Figma agent, generative plugins, and Code Layers.</p>
<p>Some of these features are open beta, some are closed beta, and some may depend on plan access. So the important thing is not only “can I use it today?”</p>
<p>The important thing is the direction.</p>
<p>Figma wants the design file to become more active.</p>
<p>Not just static screens. More like a living workspace.</p>
<h2>Code Layers may change handoff</h2>
<p>Code Layers is one of the most interesting updates for me.</p>
<p>The idea is simple but strong: code can become a layer on the canvas.</p>
<p>This can make designer and developer work closer. A designer can understand how the interface behaves, not only how it looks. A developer can also see the design context better.</p>
<p>I do not think this removes the need for developers or designers. It can remove some weak handoff moments.</p>
<p>The better question is this:</p>
<p>Can the team keep design decisions and code decisions closer?</p>
<p>If yes, this can be very useful.</p>
<h2>Motion makes interaction more visible</h2>
<p>Figma Motion is also a big step.</p>
<p>For many product teams, motion is still added late. Sometimes it is forgotten. Sometimes it is explained with comments and videos.</p>
<p>But motion is part of UX.</p>
<p>It helps users understand change, feedback, loading, direction, and hierarchy.</p>
<p>If motion becomes easier inside Figma, designers can think about interaction earlier. That is good for product quality.</p>
<p>But again, AI or presets are not enough alone. Motion still needs taste and purpose. A transition should help the user, not only decorate the screen.</p>
<h2>Shaders and 3D are not only decoration</h2>
<p>Custom shaders, effects, fills, and more visual tools can look like “visual design candy” at first.</p>
<p>But there is a serious side too.</p>
<p>Brands need more flexible visual systems. Product pages, launch visuals, app backgrounds, empty states, and marketing assets all need to move faster.</p>
<p>When these tools stay close to the design file, the designer can explore visual language without leaving the workflow too much.</p>
<p>This can be good for creative speed.</p>
<p>But I still think the same rule applies: if the system is weak, the output becomes random.</p>
<h2>Generative plugins and agent skills are about repeatable work</h2>
<p>Generative plugins are interesting because they make small custom tools easier to create.</p>
<p>Instead of waiting for a full plugin development process, a designer can ask the Figma agent to build a tool for a specific workflow.</p>
<p>This can be spacing cleanup, layer naming, shader creation, asset generation, or many small team tasks.</p>
<p>Agent skills are also important because they can give AI more context and repeatable instructions.</p>
<p>This is very close to what I wrote before in <a href="https://poryaz.com/ai-design-needs-human-prep-not-just-prompts/">AI Design Needs Human Prep, Not Just Prompts</a>.</p>
<p>AI works better when it has rules, structure, and context.</p>
<p>Without that, AI can create fast work, but not always good work.</p>
<h2>Weave tools bring AI image workflows closer</h2>
<p>Weave tools inside Figma Design are also a sign of where things are going.</p>
<p>Designers do not only need one beautiful AI image.</p>
<p>They need repeatable visual operations: background replacement, asset variations, aspect ratio changes, product visuals, and style exploration.</p>
<p>When those workflows are inside the design tool, creative production can become faster.</p>
<p>For growth teams and product teams, this matters too. More experiments can be created without opening five different tools.</p>
<h2>My take for designers</h2>
<p>Figma Config 2026 is not only a feature list.</p>
<p>It is a signal.</p>
<p>The design tool is moving toward a place where designers can work with code, AI, motion, visual systems, and reusable workflows together.</p>
<p>This can make design faster.</p>
<p>But faster is not automatically better.</p>
<p>The designer still needs to decide:</p>
<ul>
<li>what should be designed</li>
<li>what should be automated</li>
<li>what should stay simple</li>
<li>what needs human judgment</li>
<li>what should become a reusable system</li>
</ul>
<p>For me, the best designers in this new workflow will not be the ones who only know prompts.</p>
<p>They will be the ones who can prepare systems, judge output, and connect product thinking with AI tools.</p>
<p>You can follow more related posts in my <a href="https://poryaz.com/category/ai/">AI</a>, <a href="https://poryaz.com/category/ui-ux/">UI/UX</a>, <a href="https://poryaz.com/category/product-design/">Product Design</a>, <a href="https://poryaz.com/category/tools/">Tools</a>, <a href="https://poryaz.com/category/technology/">Technology</a>, and <a href="https://poryaz.com/category/growth/">Growth</a> categories.</p>
<h2>Sources</h2>
<ul>
<li><a href="https://help.figma.com/hc/en-us/articles/39582753756695-What-s-new-from-Config-2026" rel="nofollow">Figma Help: What’s new from Config 2026</a></li>
<li><a href="https://www.figma.com/release-notes/" rel="nofollow">Figma release notes</a></li>
<li><a href="https://help.figma.com/hc/en-us/articles/41147702210071-Quick-start-guide-to-generative-plugins-and-shaders" rel="nofollow">Figma Help: Generative plugins and shaders</a></li>
<li><a href="https://help.figma.com/hc/en-us/articles/40283639496599-Custom-skills-for-Figma-Make" rel="nofollow">Figma Help: Custom skills for Figma Make</a></li>
</ul><p>The post <a href="https://poryaz.com/figma-config-2026-ai-code-layers-motion/">Figma Config 2026: AI, Code Layers and Motion Change the Design Tool</a> first appeared on <a href="https://poryaz.com">Burak Poryaz - Web ve Mobil Arayüz Tasarımı - UX Ui Tasarım</a>.</p>]]></content:encoded>
					
		
		
			</item>
	</channel>
</rss>
