<?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 Pratyush Rungta on Medium]]></title>
        <description><![CDATA[Stories by Pratyush Rungta on Medium]]></description>
        <link>https://medium.com/@pratyushrungta?source=rss-429b2be51fd7------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*9287H1ZmR25KbZQO</url>
            <title>Stories by Pratyush Rungta on Medium</title>
            <link>https://medium.com/@pratyushrungta?source=rss-429b2be51fd7------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 23:55:27 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@pratyushrungta/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[Shift + A Magic ]]></title>
            <link>https://medium.com/design-bootcamp/auto-layout-2d0491a8cc84?source=rss-429b2be51fd7------2</link>
            <guid isPermaLink="false">https://medium.com/p/2d0491a8cc84</guid>
            <category><![CDATA[figma]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[css]]></category>
            <category><![CDATA[autolayout]]></category>
            <category><![CDATA[ai]]></category>
            <dc:creator><![CDATA[Pratyush Rungta]]></dc:creator>
            <pubDate>Mon, 16 Jan 2023 06:05:06 GMT</pubDate>
            <atom:updated>2023-01-17T05:23:35.917Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TIdGM0m7YV0sHDz4sFSfQw.png" /></figure><p>Shift+A, a magical shortcut that converts your design components to Auto Layout in Figma.</p><p>So, what is <a href="https://help.figma.com/hc/en-us/articles/360040451373-Explore-auto-layout-properties"><strong>Auto Layout?</strong></a></p><p>It seems like a very popular question that every new designer asks their senior: how to use it and what is its importance. However, the response they get is not always the same. Some, like me, consider Auto Layout magical, while others believe it restricts their creativity in achieving what could be achieved with Frames or Groups.</p><p>In this article, I am going to talk about its inception, how it enhances our design, makes it more accessible to developers, and the future benefits of using Auto Layout. I will also discuss how it can be a game-changer in the future with AI, and where we should not use it.</p><p>This article will not cover the learning of Auto Layout; there are tons of resources to learn it. I have mentioned a few at the end of blog.</p><h3>History of CSS</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7-RJTaiMvvkdp_HP-Nbp5Q.png" /></figure><p>If you have been around web development since the 1990s, you may remember how different web design used to be. If you have not, welcome to a better world! 😇</p><p>Solutions were often not intuitive and overly complicated, with hacky workarounds often considered best practices.</p><p>Remember those websites where everything was stacked in columns and components floated all over the place? Those methods were a nightmare in comparison to the stack we use today.</p><h3>Days of HTML Tables &amp; Floats</h3><p>In the early days of the web, people used plain HTML and complicated table formats to structure their content. It was a challenging time of invisible GIFs used for spacing, complex markup, and other awful techniques.</p><p>Then CSS arrived with its first version, bringing with it the concept of <em>float</em> to help layout webpages. This method was relatively straightforward: if you had an element that you wanted text to wrap around, you would simply float it and the desired effect was achieved. When this was combined with a fixed size for each floated element, various space-clearing techniques, and the CSS position property, a lot could be accomplished.</p><p>This allowed them to create multi-column layouts and quickly become the preferred approach. However, this hacky method may work on some devices, but not on others. With the advent of tablet and mobile devices, these hacky techniques began to fall apart, leaving developers in need of a more responsive solution that would work across all screens.</p><h3>Arrival of early Flex-box Framework</h3><p>Flex-box’s <a href="https://annairish.github.io/historicizing/history">first working draft</a> came out on July 23, 2009, offering an improvement over existing layout solutions and bringing joy to web developers and designers.</p><p>This was the first CSS property to be dedicated entirely to layouts, quickly becoming an essential part of modern web development.</p><p>It is especially effective for page layouts that are mainly composed of columns or rows. For example, if we want to line up a few elements in a single row, the <em>display: flex; </em>property gives us a modern and straightforward way of doing so.</p><h3>So…Why are you telling me this?</h3><p>The above evolution shows our arrival to the current technology for web development, which has solved a ton of previous shortcomings in website development.</p><p>Design or design tool evolution has been pretty much the same. We started with a very janky GUI to create mostly art or graphics, where we used to place everything where we felt they looked good. That’s how we learnt and have used Illustrator, Paint, or any other tool. These products’ focus was never to create UIs with a ton of constraints. It was to generate aesthetic art or graphics, and we were using them directly on a printed flex or your marriage card.</p><p>But with the evolution of digital product design, we started working with a ton of constraints, and to achieve those constraints/limitations, we had to limit our designs to a few constraints so that designers and developers could be in sync and achieve the desired result with the least effort.</p><p>This is where auto layout comes in.</p><p>Let see how auto layout is the flex-box evolution on the design tool side, and how it is so similar to flex-box, which developers use to create the UIs we design.</p><h3>Similarities between Flex-box and Auto-Layout</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jxzAypVgvXtfuGu36FEYYA.png" /></figure><p>Flex-box and Auto Layout are extremely similar. A Flex Container (Parent Frame) always holds all elements/components and keeps them aligned when resizing.</p><p>We can control how the flex container/frame grows when new items/nested frames are added. When the container/frame is horizontally oriented, the container expands from left to right by default. Similarly, when the container/frame is vertically oriented, the container expands from top to bottom by default, like with the CSS-flex property.</p><p>Auto Layout also has the Justify content attribute, which determines the alignment along the container/main frame’s axis. Items can be placed at the beginning, end, or center of the container.</p><p><em>Here is an example of a button created with Auto-Layout that outputs the CSS code which can be directly added to the code.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rAqKX_SPZUKzfuFEvzUw1Q.png" /></figure><p>The above examples show how easy it is to implement the Auto Layout-ed design in code.</p><p>Compared to a Group or Frame Design, which is just stuff floating and set without any/or some constraints.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*q3PkfSwB_xXezV0rgMCCpQ.png" /></figure><h3>Future benefits of Auto Layout</h3><p>With the boom of ChatGPT and Mid-journey, we are pretty sure that making UIs won’t be a tough task; AI can probably make it way more aesthetically pleasing than us in 1/100th of the time. Where it did lack, however, was bringing the design to the development phase.</p><p>Whatever AI will generate will be like the old design method of putting everything it collects in one place without any constraints. Where we as designers will win is by putting out a way of making design that can be easily converted to developed screens efficiently. This is where auto layout will come in. The example above shows how Auto-layout output in design is so much similar to CSS Flex-box. I am pretty sure in the future, Figma or any other tool will be smart enough to generate perfect code that can be directly attached to a backend. This means that basic UIs can be generated directly from the design tool.</p><p>Recently, <a href="https://www.framer.com/">Framer </a>came up with their Sites feature, where you can design any website on <a href="https://www.framer.com/figma/">Figma and copy it to Framer</a> to push it directly as a website in no time. If you carefully observed, they are using the Box Layout (or Auto-layout) model to achieve this very quickly and efficiently. Just try making the whole website with Auto-Layout and transfer it to Framer; you won’t have to make a slight change and you will be able to push it directly to production from design.</p><blockquote>In the future, the power of good UI will be in the hands of designers.</blockquote><h3>Mentioning the Elephant in the room</h3><p>Why are so many people not using the auto layout feature?</p><p>In most large companies, processes are well established and adapting to a new feature or way of doing things can be costly in terms of time and effort. Design knowledge transfer (KT) becomes difficult when some people use groups or frames while others use auto layout for the product.</p><p>Currently, there is no real use case for auto layout. However, with the introduction of tools like Framer, I believe that plugins and tools will eventually be developed that can generate code that is well-written enough to be used directly to build apps.</p><p>Creative limitations can also be a factor; although most things can be achieved with auto layout, there can be a lot of complications when designing with constraints. For example, a landing page would require many iterations before it is finalized, and starting with auto layout can reduce the efficiency of this process.</p><p>Nevertheless, people are not necessarily opposed to auto layout. Those I have encouraged to use it have found it to be a magical addition to their design process. They are better able to do KT with developers, knowing what will be easy for them to work on and what will be difficult.</p><h3>Conclusion</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LAYrNjV6YEJGb0KSUzOJgA.png" /></figure><p>Actually, there is no definite conclusion for this topic. Designers must strive to improve the user experience of the product, whether by designing on Paint or by using Auto-Layout; however, I believe that every designer should take more control of their work in order to stay relevant in the industry.</p><p>This can be achieved as soon as our work is more effectively implemented in the finished product, and to accomplish this we should move towards more creative techniques like prototyping, working with no-code platforms, or even Auto-Layout in some cases.</p><p>Yes, this is my opinion on Why and When to Use Auto-Layout. This is my first lengthy article, and I would appreciate any feedback.</p><p>Special thanks to <a href="https://medium.com/u/82b0b3ac6175">Neha</a> for assisting me with content touch-ups, as well as my team for their insightful feedback.</p><p>I’m also on Twitter, you can find me at <a href="https://twitter.com/PratyushRungta">@pratyushrungta</a>.</p><p><strong>Resources to learn about Auto-Layout</strong></p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FOAHOqtWwek0%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DOAHOqtWwek0&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FOAHOqtWwek0%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/3d7aec9c1417319d53e14756b7a2b2de/href">https://medium.com/media/3d7aec9c1417319d53e14756b7a2b2de/href</a></iframe><ul><li><a href="https://uxplanet.org/auto-layout-in-figma-everything-you-need-to-know-9acb11e1031c">Auto Layout in Figma -Everything You Need to Know</a></li><li><a href="https://goodpractices.design/figma-autolayout">Design good practices</a></li><li><a href="https://help.figma.com/hc/en-us/articles/360040451373-Explore-auto-layout-properties">Explore auto layout properties</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2d0491a8cc84" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/auto-layout-2d0491a8cc84">Shift + A Magic 🪄</a> was originally published in <a href="https://medium.com/design-bootcamp">Bootcamp</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>