<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Aleksei Kipin on Medium]]></title>
        <description><![CDATA[Stories by Aleksei Kipin on Medium]]></description>
        <link>https://medium.com/@aleksei_kipin?source=rss-de28b323491c------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*645h83R0mYhbhdIMeq4ICA.jpeg</url>
            <title>Stories by Aleksei Kipin on Medium</title>
            <link>https://medium.com/@aleksei_kipin?source=rss-de28b323491c------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 23:30:19 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@aleksei_kipin/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Tips and tricks for prototyping in Figma]]></title>
            <link>https://uxdesign.cc/tips-and-tricks-for-prototyping-in-figma-a3e5de19d1?source=rss-de28b323491c------2</link>
            <guid isPermaLink="false">https://medium.com/p/a3e5de19d1</guid>
            <category><![CDATA[figma]]></category>
            <category><![CDATA[interaction-design]]></category>
            <category><![CDATA[ui]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[prototyping]]></category>
            <dc:creator><![CDATA[Aleksei Kipin]]></dc:creator>
            <pubDate>Wed, 06 May 2020 11:23:35 GMT</pubDate>
            <atom:updated>2020-05-06T11:40:07.780Z</atom:updated>
            <content:encoded><![CDATA[<h4>In this article I will share a few tips and tricks that I use to make prototyping in Figma even more helpful and easier to use. Before we start I want to say that prototyping in Figma for me is pure joy, but we can always improve things, right? Let’s keep it short and sweet and dive into details straight away.</h4><figure><img alt="Cover" src="https://cdn-images-1.medium.com/max/1024/1*nlluj3xFUbBabcDGJMCs2A.png" /></figure><h3>Custom transitions and micro-interactions</h3><p>Yep, I know that there are a lot of useful built-in transition effects in Figma already, but here I want to talk about custom micro-interactions, complicated transitions and show you how to add them into your Figma prototypes. Let’s take a look at a couple of examples I’ve prepared.</p><figure><img alt="An example of a transition #1" src="https://cdn-images-1.medium.com/max/1024/1*VRFivl105GieZ2W7FCK6Bw.gif" /></figure><figure><img alt="An example of a transition #2" src="https://cdn-images-1.medium.com/max/1024/1*wIdJ9Uw7xzvnwlBgAgueig.gif" /></figure><p>To make this kind of interaction you need Figma and any animation tool of your choice. I used After Effects just because I’m familiar with it.</p><figure><img alt="After Effects project" src="https://cdn-images-1.medium.com/max/1024/1*K5t1Ly_ow9_x4cA1Zu_hHw.png" /></figure><p>When you have your animated transition, add it to your project between the screens that you want to animate and link them. For the animated layers use the after delay property— the delay should be equal to the length of the animated transition you have. In the end it should look like this.</p><figure><img alt="An example of how it looks like in Figma" src="https://cdn-images-1.medium.com/max/1024/1*V4gR9dvgmqtKkSYQ2vV_ew.png" /><figcaption>Illustrations: <a href="https://www.openpeeps.com/">https://www.openpeeps.com/</a></figcaption></figure><p>If you’re not familiar with any animation tools or simply don’t have any animation software installed on your machine you can do a lot of stuff with Figmotion. <a href="https://www.figma.com/community/plugin/733025261168520714/Figmotion">Figmotion</a> is a Figma plugin that helps you animate your designs in Figma without using any third-party software. Here’s an example of how it works:</p><figure><img alt="An example of how Figmotion works in Figma" src="https://cdn-images-1.medium.com/max/1024/1*gstchkrIbnhoVxpvGILbZA.gif" /><figcaption>Figmotion</figcaption></figure><h3>Improve navigation between flows in prototyping mode</h3><p>When I work on a user story, even if it’s the most simple user story in the world, I have at least a few edge cases or validation points that I need to show to the team so we can discuss it. It’s quite frustrating in Figma at the moment. I’ve tried different approaches:</p><ol><li>I tried to keep my flows in one file and change the starting frame by moving the little blue play button between frames. But it’s inconvenient to find and move this little square when you are showing something to the team plus the loading time. It’s so slow when you reload your prototype (especially if you work with a big file).</li><li>Then I tried to split my design files into a few smaller ones and keep open a prototyping tab for each of them. That’s a pain. If the user story you’re working on is big and complicated (it implies a lot of edge cases and different scenarios) Figma can’t keep all prototyping tabs open and reloads them when you present them to the team. On top of that, it’s very hard to navigate between a lot of opened tabs (1 tab per flow * 2 because of the opened prototype window).</li></ol><p>Here is the best solution that I’ve found. I’ve designed a navigation screen that I put as a first screen in all my prototypes.</p><figure><img alt="A navigation index page" src="https://cdn-images-1.medium.com/max/1024/1*OeCEJ-S6CUaRj4uaTZZOqA.png" /></figure><h3>Grouping flows within one file</h3><p>As I mentioned above I always have at least a few flows related to a user story. That’s why I need a way to organize them within one file. To do it I designed a simple element that helps a lot.</p><figure><img alt="A flow header" src="https://cdn-images-1.medium.com/max/1024/1*i1U4tV7RGojYYO-3IRgd0g.png" /></figure><figure><img alt="An example of how these navigation hacks work" src="https://cdn-images-1.medium.com/max/1024/1*R7HbQdyuF1P7OvAFSdPZ4w.png" /></figure><h3>Hand-off</h3><p>Sometime I have details related to the implementation of my design files that I need to pass on to the engineers and they usually work better next to the mockups. That’s why I made a post-it note component and I use it to specify details related to the implementation of my design.</p><figure><img alt="Hand-off process with the post-it note component" src="https://cdn-images-1.medium.com/max/1024/1*4DaXNdAtBv42-Yyv6T7nyg.png" /></figure><p>I have all three components that I mentioned above in my UI components library in Figma. It allows me to access them quickly from any file I’m working on.</p><figure><img alt="A screenshot of my UI library" src="https://cdn-images-1.medium.com/max/1024/1*1s3Fl6ram3H8v_Aq16g7zg.png" /></figure><p>Here is a link to a Figma file with the examples that I’ve mentioned: <a href="https://www.figma.com/file/3sL1cg4kEKQBa9NbWK7nOP/transitions-medium?node-id=0%3A1">Figma link</a>. Thank you for reading and I hope you found this useful. Feel free to reach out to me on <a href="https://dribbble.com/kipin"><strong>dribbble</strong></a> or <a href="http://twitter.com/aleksei_kipin"><strong>twitter</strong></a>.</p><p><em>Originally published at </em><a href="https://chainstack.com/prototyping-in-figma-tips-and-tricks/"><em>https://chainstack.com</em></a><em> on May 5, 2020.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a3e5de19d1" width="1" height="1" alt=""><hr><p><a href="https://uxdesign.cc/tips-and-tricks-for-prototyping-in-figma-a3e5de19d1">Tips and tricks for prototyping in Figma</a> was originally published in <a href="https://uxdesign.cc/">UX Collective</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Using auto-layout components in Figma]]></title>
            <link>https://uxdesign.cc/auto-layout-components-in-figma-110b170b9367?source=rss-de28b323491c------2</link>
            <guid isPermaLink="false">https://medium.com/p/110b170b9367</guid>
            <category><![CDATA[figma]]></category>
            <category><![CDATA[design-systems]]></category>
            <category><![CDATA[visual-design]]></category>
            <category><![CDATA[prototyping]]></category>
            <category><![CDATA[atomic-design]]></category>
            <dc:creator><![CDATA[Aleksei Kipin]]></dc:creator>
            <pubDate>Tue, 10 Mar 2020 08:45:59 GMT</pubDate>
            <atom:updated>2020-05-01T13:26:18.630Z</atom:updated>
            <content:encoded><![CDATA[<h4>I’ve been playing around with Figma Auto Layout components for a while. Here I will show how to create a full-page component using Auto Layout in Figma.</h4><figure><img alt="Post cover with an animated auto layout components" src="https://cdn-images-1.medium.com/max/1024/1*c11tljsJE5_ylnxRUwPmtQ.gif" /></figure><p>I’m a big fan of atomic design because it works well for designers, and it brings us closer to the approach that front-end developers use in their work. While we use the same approach, we can collaborate more effectively. With this in mind, I was trying to find a way to maximize the usage of the atomic design in my components library, and finally with the new Auto Layout it’s possible. Let’s take a look at what I’ve learned.</p><h3>The approach</h3><p>If you aren’t familiar with the atomic design concepts, I highly recommend you to read more about <a href="https://atomicdesign.bradfrost.com/">atomic design</a> first.</p><figure><img alt="Atomic design phylosophy at a glance" src="https://cdn-images-1.medium.com/max/1024/1*taiBGV_MrG4zsCcSbvrN_A.png" /><figcaption>Atomic design applied to the native mobile app Instagram. <a href="https://atomicdesign.bradfrost.com/">Source: https://atomicdesign.bradfrost.com/</a></figcaption></figure><p>The picture above illustrates the logic that I use for my components. With this approach, it’s easy to design components and–what is very important–to support them after.</p><p>Below you can see the page I’ll use as an example. That’s a real page that I’ve designed and use in the project I’m working on at <a href="http://chainstack.com/"><strong>Chainstack.com</strong></a>. In this post I’ll focus only on the components that use Auto Layout.</p><p><em>If you don’t want to dive into details, I put a link to the final result in Figma at the end of this post.</em></p><figure><img alt="An animation that shows how auto layout components work" src="https://cdn-images-1.medium.com/max/1024/1*5SOrnD0BTYj3pz48wwOr_g.gif" /></figure><h3>Atoms</h3><p>On the atomic level, everything is quite simple. I highlighted the components that use Auto Layout.</p><figure><img alt="A frame in Figma with atomic level components in it" src="https://cdn-images-1.medium.com/max/1004/1*5FNQK1HXivOEkuon1bYATA.png" /></figure><p>Let’s take a look at their anatomy. Text styles and colors defined in Figma Styles.</p><figure><img alt="Atom component anatomy" src="https://cdn-images-1.medium.com/max/1024/1*Kwz6hOy2QuszNx-A6HMqUQ.png" /><figcaption>Atom component anatomy</figcaption></figure><p>That’s a typical atomic level component. Auto Layout: Horizontal, Spacing Between Items 8px.</p><h3>Molecules</h3><p>Here the things are getting a bit more challenging. For our molecules, we use only the atoms that we’ve created at the previous step and some of the base elements that I’ve created in my library (font &amp; color styles).</p><figure><img alt="A frame in Figma with molecular level components in it" src="https://cdn-images-1.medium.com/max/1024/1*xE4MNe3aIZZRbZ5rwzslHA.png" /></figure><p>The hint bar is the most challenging element here. I use it on a few different pages on the platform, and it behaves differently accordingly to the situation. It should:</p><ul><li>Fit to the content size.</li><li>Take the full width of the content area</li><li>Support multi-line text for both scenarios above.</li></ul><p>You can’t simply resize an Auto Layout component in Figma, but I don’t want to keep two very similar components in my library. I found a solution.</p><figure><img alt="An animation that shows how resizable auto layout components work" src="https://cdn-images-1.medium.com/max/1024/1*AGQQENiGPGBJX1vswuUXng.gif" /><figcaption>Resizable auto layout component</figcaption></figure><p>How it works:<br>I have an Auto Layout component that adjusts its size to the content, but it sits in a component without Auto Layout, so I can resize the parent component manually if I need to adjust it to the page width.</p><figure><img alt="A molecule component in Figma" src="https://cdn-images-1.medium.com/max/1024/1*Va8d_U24kIAUffjr79C6CA.png" /></figure><p>The rest of the components are quite simple.</p><p>The breadcrumbs component, for example, is a stack of atomic components that behave in the same way as its children: atoms adjust their size to the content &gt; the breadcrumbs component adjusts its size to the size of atoms inside.</p><figure><img alt="A molecule component in Figma" src="https://cdn-images-1.medium.com/max/1024/1*wHnoJmZt7dpMCH_GP3PkTg.png" /></figure><figure><img alt="An animation that shows how molecule components work" src="https://cdn-images-1.medium.com/max/1024/1*gbo1oL44I2WMIhr-c6VW1Q.gif" /></figure><p>The buttons block works in the same way. It’s an Auto Layout component with a few atomic buttons components inside.</p><figure><img alt="An animation that shows how molecule components work" src="https://cdn-images-1.medium.com/max/1024/1*jFdn0_HyZjj-uunjnphtcQ.gif" /></figure><h3>Organisms</h3><figure><img alt="A frame in Figma with organisms level components in it" src="https://cdn-images-1.medium.com/max/1024/1*R-vEAZHgk0YszRlHi5Hugg.png" /></figure><p>The most challenging part here was to organize the details section: it should support multi-line parameters. This means that all blocks should behave according to the amount of content the blocks above have. It can have from one to three rows of parameters, so we need to support any configurations within these limits:</p><ul><li>From 1 to 3 rows</li><li>Rows can have 4 blocks of information or less</li></ul><figure><img alt="An organism level component in Figma" src="https://cdn-images-1.medium.com/max/1024/1*wuyh8IYs2fuH8BmCbhg_RQ.png" /></figure><p>The first layer helps us to create paddings around the content.</p><figure><img alt="An organism level component in Figma" src="https://cdn-images-1.medium.com/max/1024/1*Ix4yihgdyl5Z4peD7VMcTQ.png" /></figure><p>This layer split the content section from the section header (“Details”).</p><figure><img alt="An organism level component in Figma" src="https://cdn-images-1.medium.com/max/1024/1*AQAeANa2kgthHNgBGjNZ3A.png" /></figure><p>Here we create paddings between the rows with a few atomic design components inside.</p><figure><img alt="An organism level component in Figma" src="https://cdn-images-1.medium.com/max/1024/1*fAZBjLXJ0hKPMh_xAQooIw.png" /></figure><p>The final level is a <em>row</em> component with a few atomic design components inside. It behaves in the same way as the breadcrumbs component.</p><p>Another big organism is a table component, but it’s much simple. Here we need the first Auto Layout component to separate the header from the body.</p><figure><img alt="An organism level component in Figma" src="https://cdn-images-1.medium.com/max/1024/1*BOndbYlh6G5A2KUh8Z3DkQ.png" /></figure><p>Then I use Auto Layout with 0 spacing to make the table.</p><figure><img alt="An organism level component in Figma" src="https://cdn-images-1.medium.com/max/1024/1*SmEM2Pmy6Op2OBRtqfgDUw.png" /></figure><h3>Templates</h3><p>The template has a content section where we collect all dynamic elements and a few components that sit in their places (breadcrumbs, section header).</p><figure><img alt="A template level component in Figma" src="https://cdn-images-1.medium.com/max/1024/1*h2GEajS58pbB_OFAcXGBeA.png" /></figure><figure><img alt="The main header component" src="https://cdn-images-1.medium.com/max/1024/1*l2t5xLgpDD25YJasrhZT6Q.png" /><figcaption>The main header</figcaption></figure><p>I didn’t add the main header to the final template because components in Figma don’t support <em>fix position when scrolling</em> for its elements. This is the only reason that doesn’t allow us to use this page as a component, but it’s not a problem for short pages that fit 100% of its content to the screen.</p><p>Now we have a very flexible, easy to support page. This is how it looks like in the end.</p><figure><img alt="An animation that shows how the final full page component works" src="https://cdn-images-1.medium.com/max/1024/1*jG-T8jicQuZ2gPDmalLEug.gif" /></figure><p>In the animation above you can see how our atomic design page works in the prototyping mode in Figma.</p><figure><img alt="The final full page component in Figma" src="https://cdn-images-1.medium.com/max/1024/1*K2pB2oinEhctpX8nTYClXQ.png" /></figure><p>That’s how simple and clean the page looks. On top of that, all components on the page are very flexible and responsive, and I can use them across all my design files. In case of any changes in the design of the page, I can update them in my library and it will update all my design files automatically.</p><p>Here is a link to the page: <a href="https://figma.fun/EJjLnl">https://figma.fun/TxDFA4</a></p><h3>P.S.</h3><p>Figma suggests using an automatic Auto Layout creation (press <em>Shift + A</em>) for simple components, and usually it works well, but sometimes it doesn’t work as expected. Instead of removing the background layer and replicating it with Auto Layout parameters, Figma thinks that it’s an object that’s supposed to be a part of the component that we’re trying to create. You can see an example of this behavior below. In this case, I create the Auto Layout component manually.</p><figure><img alt="An animation that shows the bug that the author described in the P.S" src="https://cdn-images-1.medium.com/max/480/1*dNJCSRswAI1Cj_PIbf2JLA.gif" /></figure><p>Thank you for reading and I hope you found this useful. Feel free to reach out to me on <a href="https://dribbble.com/kipin"><strong>dribbble</strong></a> or <a href="https://twitter.com/aleksei_kipin"><strong>twitter</strong></a>.</p><p><em>Originally published at </em><a href="https://chainstack.com/auto-layout-components-in-figma/"><em>https://chainstack.com</em></a><em> on March 9, 2020.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=110b170b9367" width="1" height="1" alt=""><hr><p><a href="https://uxdesign.cc/auto-layout-components-in-figma-110b170b9367">Using auto-layout components in Figma</a> was originally published in <a href="https://uxdesign.cc/">UX Collective</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>