<?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 Alex Mnohosmyslov on Medium]]></title>
        <description><![CDATA[Stories by Alex Mnohosmyslov on Medium]]></description>
        <link>https://medium.com/@mnohosmyslov?source=rss-89bf5edc5d8c------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*EL51oB3KWYIWR3OCFKAUrA.jpeg</url>
            <title>Stories by Alex Mnohosmyslov on Medium</title>
            <link>https://medium.com/@mnohosmyslov?source=rss-89bf5edc5d8c------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 05:03:50 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@mnohosmyslov/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[Designer Evolution: The Presence Effect]]></title>
            <link>https://mnohosmyslov.medium.com/%D1%8D%D0%B2%D0%BE%D0%BB%D1%8E%D1%86%D0%B8%D1%8F-%D0%B4%D0%B8%D0%B7%D0%B0%D0%B9%D0%BD%D0%B5%D1%80%D0%B0-%D1%8D%D1%84%D1%84%D0%B5%D0%BA%D1%82-%D0%BF%D1%80%D0%B8%D1%81%D1%83%D1%82%D1%81%D1%82%D0%B2%D0%B8%D1%8F-c3a963e2452a?source=rss-89bf5edc5d8c------2</link>
            <guid isPermaLink="false">https://medium.com/p/c3a963e2452a</guid>
            <category><![CDATA[product]]></category>
            <category><![CDATA[audio]]></category>
            <category><![CDATA[videos]]></category>
            <category><![CDATA[sound-design]]></category>
            <category><![CDATA[mastering]]></category>
            <dc:creator><![CDATA[Alex Mnohosmyslov]]></dc:creator>
            <pubDate>Wed, 20 Jun 2018 07:31:15 GMT</pubDate>
            <atom:updated>2024-08-18T12:40:58.758Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KrJpU24lN2ROvLts9uCEZg.png" /></figure><p>Here we come to the third step in the development of a designer as a technical specialist. And this time we will talk about <strong>Sound Design</strong>.</p><p>Someone will say “it’s simple, we take sounds from stocks and throw everything into the app”. Someone will use just two audio tracks (for example, music and voice) and send them to the renderer with the words “it’s done”. However, all this is not as easy as it seems. I suggest to understand some aspects of this industry.</p><p>Let me make it clear right away that not everyone will need this type of activity, but if you want the user to dive deeper into the application or video — you’re welcome.</p><p>Why do we need Sound Design? It creates the realism of what is happening, creating a presence effect for the user/client. Humans are designed in such a way that a person needs sound feedback and we are used to hearing both background noises and accent sounds. When used correctly (e.g. to attract a client), sound support enhances the desired emotional background, which can <strong>positively contribute to business</strong> ;)</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fplayer.vimeo.com%2Fvideo%2F256423405%3Fapp_id%3D122963&amp;dntp=1&amp;url=https%3A%2F%2Fvimeo.com%2F256423405&amp;image=https%3A%2F%2Fi.vimeocdn.com%2Fvideo%2F684083952_640.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=vimeo" width="720" height="720" frameborder="0" scrolling="no"><a href="https://medium.com/media/86785bed390bfca9e3a8c9fa9eba05dc/href">https://medium.com/media/86785bed390bfca9e3a8c9fa9eba05dc/href</a></iframe><p><strong>The problem…</strong></p><p>Since the range of Sound Design usage is really wide, let’s consider the problem in relation to two specializations.</p><p>1. <strong>Interface design</strong>. It is quite rare nowadays to find an application that will respond to the user’s actions with sounds. Although such a response would be a pleasure to the user, and sometimes an assistant to use. Take, for example, the standard mail app on iOS — when a letter is successfully sent, the interface is accompanied by a corresponding sound and, without even looking at the screen, the user realizes that everything has been successful. Most often, applications are limited to custom sounds for notifications.</p><p>2. <strong>Motion Design</strong>. No matter how beautiful the animation is, it is hard to fully experience it without sound. If these are splashes, movements, blows — the video sequence must be accompanied by appropriate sounds. This is the only way we can convey the reality of what is happening. However, in this direction, the problem is no longer the lack of sounds, but their improper application and processing.</p><p><em>Did you also get annoyed when the special effects in the movie interrupted the characters’ voices?</em></p><p>Why is that? Making a high-quality and harmonious set of sounds for the entire application is <strong><em>difficult, expensive, and time-consuming</em></strong><em>.</em></p><p>The whole process is done completely manually and there is no automation to speak of. Each file has to be adjusted separately, because all sounds are very unique. Your ears get tired quickly and it’s hard to know if you’re doing a good job or not, if you’re hearing the right noise or not. You need a lot of patience and diligence in this business.</p><blockquote>Nothing should distract the viewer from what is happening on the screen. Sound design should be organic.</blockquote><p>Therefore, you should keep in mind some rules:</p><p><strong>Sound type.</strong> You should ask yourself: what is the purpose of this particular sound: background noise, emphasis, or just an effect? Also, do not forget that <a href="https://en.wikipedia.org/wiki/Colors_of_noise"><em>some noises</em></a> calm a person, some do the opposite.</p><p><strong>Volume.</strong> There should be no sharp jumps in the volume of the sound wave, even the most accented sounds should not stand out too clearly in the spectrum. If you want to amplify a specific sound, it is better to weaken the others.</p><p><strong>Equalization.</strong> It is very important to remember what frequencies your sounds are at. When synchronizing several sounds, it is worth checking: will one sound drown out another? Will it be too loud or bassy? How well will it be heard in the speakers / headphones / phone speaker?</p><p><strong>Space.</strong> We are in a three-dimensional space, which means all sounds must be in stereo. It is necessary to understand at what point in the video sequence the sound should be played from a certain place. It can be far or close, left or right, etc. And only the voiceover of the announcer should be in mono mode, since he addresses the viewer directly, like an audience.</p><p>I think this will be enough to start with, and later on you should pay attention to compression, reverb, filtering, etc.</p><p><strong>Where to start when it comes to an app?</strong></p><p>You have to see the aesthetics. You have to go from what you see on the screen to imagine what it might sound like.</p><p>If it’s a minimalist design, I’d go for clean and short futuristic/electronic sounds. If there’s a historical design background, acoustic/stringed instruments would be more appropriate. It’s all pretty logical.</p><p>It is worth remembering where this sound will be played. For example, phone speakers are on average in the following range: 500 Hz — 12 kHz. This means that the user will not even hear sounds that are outside these limits.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/548/1*RWFtoKRNJKoY0S582MVsOQ.png" /><figcaption><em>Approximate range of frequencies that can be heard from the phone speaker</em></figcaption></figure><p><strong>Where to start when it comes to a video?</strong></p><p>You need to decide on the mood, message and atmosphere of the video sequence. For sound design we will need: background music, voiceover, a set of sounds and noises that will complement reality. Searching, selecting and processing background noises is a very painstaking process. You can spend hours selecting sounds of the city and nature, although they all sound like “pshshshshsh…”, but for the viewer it will still be a pleasant and realistic addition to the scene.</p><p>Now let’s prioritize them:</p><ol><li>Voiceover</li><li>Set of sounds and noises</li><li>Background music</li></ol><p>All audio tracks must be set by volume (mixing process). Thus, the voiceover of the speaker (the highest priority) must always be heard and very clearly. In addition to the fact that it will be the loudest element, nothing should interfere with it in the frequency range. To achieve this, open the equalizer and start looking at where the most useful frequencies are that cannot be drowned out. Usually for a voice, these are mid frequencies (but we remember that each voice is unique).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/533/1*TBKp9xXxGLi_DyxFiHK9_A.png" /><figcaption><em>Voice Analysis. From 500 Hz to 1500 Hz the voice is clearly audible, there are more extraneous sounds on the sides that have little effect on the clarity of pronunciation</em></figcaption></figure><p>This way we can see where the most useful data is, which means we need to make room for these frequencies. To do this: we need to put down these frequencies in background music and various noises.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/533/1*ud6FvLOekJ7X4pNw_oR-0w.png" /><figcaption>Mute frequencies in background music. The gray color of the spectrum shows what it was before the change, purple — after. A space has appeared, which will be perfectly complemented by the voice of the announcer.</figcaption></figure><p>By following these rules, you can take care of the sound design of your product. Whether it’s an app, a video, an interactive advertisement or anything else. The tool to do all this is any digital audio workstation (e.g. Logic Pro, Ableton Live, FL studio, etc). Thankfully, there are plenty of tutorials on this kind of apps nowadays.</p><p>P.S. Is there really nowhere for a designer to develop further? Of course, there is. In this series, I talked specifically about <em>the technical</em> direction and my experience. And there is always room for development, because there are so many related industries ;)</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c3a963e2452a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Designer Evolution: Dynamics Production]]></title>
            <link>https://mnohosmyslov.medium.com/%D1%8D%D0%B2%D0%BE%D0%BB%D1%8E%D1%86%D0%B8%D1%8F-%D0%B4%D0%B8%D0%B7%D0%B0%D0%B9%D0%BD%D0%B5%D1%80%D0%B0-%D0%BF%D1%80%D0%BE%D0%B8%D0%B7%D0%B2%D0%BE%D0%B4%D1%81%D1%82%D0%B2%D0%BE-%D0%B4%D0%B8%D0%BD%D0%B0%D0%BC%D0%B8%D0%BA%D0%B8-2a97cf607f30?source=rss-89bf5edc5d8c------2</link>
            <guid isPermaLink="false">https://medium.com/p/2a97cf607f30</guid>
            <category><![CDATA[after-effects]]></category>
            <category><![CDATA[motion-design]]></category>
            <category><![CDATA[animation]]></category>
            <category><![CDATA[expression]]></category>
            <category><![CDATA[product]]></category>
            <dc:creator><![CDATA[Alex Mnohosmyslov]]></dc:creator>
            <pubDate>Wed, 18 Apr 2018 08:25:49 GMT</pubDate>
            <atom:updated>2024-08-20T19:29:18.518Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jlRWbs1Bz5wQkudq6sR3gg.png" /></figure><p>There are countless design solutions for a product. Convenient and beautiful or not so much. But they all lack one property: they have no life in them. It is difficult to surprise with a static picture today, so the Motion Design comes into service.</p><p>I suggest figuring out: what is it, why does a designer need it, and where to apply it?</p><p><strong>The problem…</strong></p><p>Animation is important, first of all, not to make a high-quality publication on Dribbble, Behance, etc., because most often the content of these services is just pictures (or beautiful animations), which do not solve the user needs.</p><p>In fact, it is needed to make it easier for the user to perceive information and less stressful for the brain. With the help of animation you can increase the usability of the interface and make the work with it smooth, pleasant, meaningful, as well as to emphasize some element. But here you should be careful not to overdo it, because any animation should carry its own meaning, not just overload the interface with all sorts of “whistles”.</p><p>Motion Design is the art of bringing graphics to life through animation. It is quite a wide-profile branch, as it includes design, animation, directing, visual and sound effects. With its help we create full-fledged media content, not just animation.</p><p>Moreover, today this profession is becoming more popular, and a designer simply needs these skills. Why only now? It’s simple — because now technologies are ready for it. New lossless video compression codecs have appeared, mobile Internet is developing, Facebook has allowed uploading animated covers and avatars, and much more.</p><p>Why is animation so useful in a product? With its help, we communicate with the user at the level of sensations, prompt him what to pay attention to, demonstrate the process of transition from one content to another. In this sense, we work as a director, where, in addition to the general scenario, we must work out all the details, right down to the trajectory of the object’s movement (and as we know, the trajectory depends on many physical properties that cannot be neglected). You can draw an analogy with vision. We perceive information continuously, looking at something, and only at the moment of blinking there are short pauses. If we blink and find ourselves in a completely different place with a different picture in our eyes, we will, at the very least, be scared. Therefore, this should not be in the product.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/350/1*vq3C_Jut9lELOTsh13OPzQ.gif" /></figure><p>Conclusion: without knowledge of motion design, it will be impossible to create a truly living product that will be easy and pleasant to use, and most importantly, you will want to return to it.</p><p>Let’s imagine a situation: we have developed a set of animations in a product to simplify interaction with it, and the next step is to hand it all over to development. But here’s the problem: how can we explain to a developers, for example, that the movement in the animation should be a little smoother, but not that much? It sounds funny, but that’s often how it happens. After all, when we create animation, we rely on our feelings.</p><p>And in continuation of the previous article, I would like to note that we should think about how the developers will implement the animation even before we start working on it, because there may be some limitations or difficulties on the systems, and it will be difficult for the developer to explain in simple terms how exactly to get the desired result. How to be?</p><blockquote>PS: <em>How to implement animations is a topic for a separate and rather large article. In this one, we will consider how technical knowledge can help us with this.</em></blockquote><p>Could we, as already skilled designers with some knowledge of development, describe the animation in code? Or at least make a list of parameters and how they change over time?</p><p><strong>Of course yes!</strong></p><p>Let’s look at an example of animation where there will be no animation key, and all actions will be described by code. As a reference, we will take the Dock Magnification Effect from macOS:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/741/1*UF2iOQERJC2_4ZUYI9hnrw.gif" /></figure><p>But let’s make a simplified version:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/923/1*WEfNXg4xzTKw_KgzL7h-yQ.png" /></figure><p>Let’s analyze the behavior of icons: they change their size (icon scale) depending on the cursor position (arrow position).</p><p>For further work we will need two parameters:</p><ul><li><em>factor_scale</em> (icon size change factor);</li><li><em>factor_distance</em> (the distance from the cursor to the icon at which the icon size will begin to change).</li></ul><p>I’ll use Adobe After Effects for this animation.</p><p>In order not to hardcode these values, let’s put them in variables on a separate layer. Changing them at any time will change the animation for all icons that are tied to these parameters. To do this, create a new <em>Adjustment layer</em> (<em>Layer -&gt; New -&gt; Adjustment layer</em>) called “Controls” and apply the “Slider” effect to this layer twice. This effect simply stores the slider variable inside the layer so that they can be accessed from the outside.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/231/1*mHXW4EA5k7jk23ie3BEDnQ.png" /></figure><p>To use these values inside the layer we want to animate (in this case, each icon), we need to write the following code (in JavaScript):</p><pre>factor_scale = thisComp.layer(“Controls”).effect(“factor_scale”)(“Slider”);</pre><pre>factor_distance = thisComp.layer(“Controls”).effect(“factor_distance”)(“Slider”);</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*m1pD5DRBqzn7u3HrvTmS0A.gif" /><figcaption><em>Click on the “clock” icon while holding down the Alt key to activate expressions</em></figcaption></figure><p>Let’s decipher what is written:</p><p>We create a variable <em>factor_scale</em> and set it to the value found in:</p><p><em>thisComp</em> — this composition;</p><p><em>.layer(“Controls”)</em> — Controls layer;</p><p><em>.effect(“factor_scale”)</em> — factor_scale effect;</p><p><em>(“Slider”)</em> — the Slider parameter.</p><p>And the same for <em>the factor_distance</em> variable . Nothing complicated, right?</p><p>Let’s think further: what other parameters do we need?</p><ul><li>Current icon’s Scale — we will change it eventually;</li><li>Current icon’s Position — to calculate the distance to the cursor;</li><li>Current cursor’s Position — to calculate the distance to the icon.</li></ul><pre>icon_position = transform.position;</pre><pre>icon_scale = transform.scale;</pre><pre>arrow_position = thisComp.layer(“cursor”).transform.position;</pre><p>Now we need to calculate the distance from the cursor to the icon:</p><pre>delta = length(arrow_position, icon_position);</pre><p>And you can round this value so that they are not fractional. In this case, it is more correct to write:</p><pre>delta = Math.round(length(arrow_position, icon_position));</pre><p>Now comes the fun part. Make the icon grow larger if the distance from it to the cursor becomes less than factor_distance. The <em>linear(d, dMin, dMax, value1, value2)</em> function will come to the rescue.</p><p>Let’s consider the parameters:</p><p><em>d</em> — Distance from one object to another (in our case, from the cursor to the icon);</p><p><em>dMin</em> — The minimum distance value up to which the current object will be transformed;</p><p><em>dMax</em> — The maximum value of the distance to which the current object will be transformed;</p><p><em>value1</em> — The value of the parameter at the minimum distance between objects;</p><p><em>value2</em> — The value of the parameter at the maximum distance between objects;</p><p>For our needs it will look like this:</p><pre>linear(delta, 0, factor_distance, icon_scale*factor_scale, icon_scale);</pre><p>Let’s see what we got in the end. We don’t have any animation keys, and here’s what happens if you move the cursor:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/709/1*-jX6jrrmXrpZ63RRsSjvMA.gif" /></figure><p>The final code was only 7 lines long:</p><pre>factor_scale = thisComp.layer(“Controls”).effect(“factor_scale”)(“Slider”);</pre><pre>factor_distance = thisComp.layer(“Controls”).effect(“factor_distance”)(“Slider”);</pre><pre>icon_position = transform.position;</pre><pre>icon_scale = transform.scale;</pre><pre>arrow_position = thisComp.layer(“cursor”).transform.position;</pre><pre>delta = Math.round(length(arrow_position, icon_position));</pre><pre>linear(delta, 0, factor_distance, icon_scale*factor_scale, icon_scale);</pre><p>And the final result:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xPXjuMAHb5ABmhPZBeVnYg.gif" /></figure><p>This is how you can make a keyless and fully code-described animation in fairly simple iterations. Developers don’t have to invent anything new, because they have all the parameters and relationships that describe the animation. This way, we speed up the implementation process and improve mutual understanding within the team.</p><blockquote>PS: <em>implementing the same animation using keyframes and without using code is extremely problematic, and making edits will be even more difficult. Therefore, try to automate such moments.</em></blockquote><p>You can see the result on <a href="https://github.com/mnogosmyslov/AE-Expressions-Dock-Magnification-Effect">GitHub</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2a97cf607f30" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Designer Evolution: Technical Approach to Process Design]]></title>
            <link>https://mnohosmyslov.medium.com/%D1%8D%D0%B2%D0%BE%D0%BB%D1%8E%D1%86%D0%B8%D1%8F-%D0%B4%D0%B8%D0%B7%D0%B0%D0%B9%D0%BD%D0%B5%D1%80%D0%B0-%D1%82%D0%B5%D1%85%D0%BD%D0%B8%D1%87%D0%B5%D1%81%D0%BA%D0%B8%D0%B9-%D0%BF%D0%BE%D0%B4%D1%85%D0%BE%D0%B4-%D0%B2-%D0%BF%D0%BE%D1%81%D1%82%D1%80%D0%BE%D0%B5%D0%BD%D0%B8%D0%B8-%D0%BF%D1%80%D0%BE%D1%86%D0%B5%D1%81%D1%81%D0%B0-cd16bb1bac97?source=rss-89bf5edc5d8c------2</link>
            <guid isPermaLink="false">https://medium.com/p/cd16bb1bac97</guid>
            <category><![CDATA[development]]></category>
            <category><![CDATA[workflow]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Alex Mnohosmyslov]]></dc:creator>
            <pubDate>Tue, 10 Apr 2018 06:04:50 GMT</pubDate>
            <atom:updated>2024-08-20T19:48:45.387Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Mw7cWXILNBTPsh3W9hIOog.png" /></figure><p>The main goal of this approach is a quality and timely product. Any changes will take a fairly small amount of time. However, everything is in order.</p><p><strong>The problem…</strong></p><p>Designers are rarely technical specialists, so their approach to building the process is more creative. We are faced with an unstructured project, a lack of naming layers, and other inconveniences. It is easy for a person who has discovered such a project for the first time to get lost in it (and such situations are frequent when working in a team).</p><p>Where did this problem come from? It’s probably because you forget about the structure while creating. And if you look at Adobe Illustrator, you think about layers at the very last moment (especially about the names of objects and groups). This has migrated to other software. As a result, we get something like this:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/340/1*fG94crS2nNSsfoZj3C_gIQ.png" /><figcaption><em>Not very comfortable, right?</em></figcaption></figure><p>And how much time is wasted writing style guides afterwards — I don’t even want to imagine. However, these are most likely not the only reasons for the problem. You can offer your options in the comments.</p><p>Let’s imagine if we thought about the architecture of a product at the last stages of development. It would be horrible, isn’t it? There would be no scalability, heavy support, and constant bug fixing. Only the one who developed it would not get confused when navigating such a project. And that means you can forget about teamwork.</p><p>Okay, you can make designers care about the project’s structure, and that’s it. So why does a designer need technical knowledge? You might think that we are making a single-skilled person a multi-tasker. However, this is far from true. Technical knowledge empowers you, it makes you capable of understanding and contributing to the entire project, not just your part.</p><p>The point is that knowing programming and programming directly are two different things. No one forces you to do it, but you must know it. For instance, understanding how CSS affects the layout of a webpage or how different file formats impact the quality of an image is part of this technical knowledge. Knowing the basics of programming, languages, and technologies shouldn’t be optional for a designer, and here are the reasons why:</p><ul><li><strong>Deep process understanding</strong>. Knowing how the system works helps you make faster and better decisions. Thus, when solving a task, you can choose several options and already understand how long it will take to implement such a feature and whether it will be problematic. You can improve the work of elements and the speed of your product;</li><li><strong>Accelerating teamwork</strong>. A unified design system in a team is a must-have for work. Readable and identical structure in all projects, automatic updating of layouts in case of edits;</li><li><strong>Common language with developers.</strong> “It can’t be done” they used to say. Now, you will understand that it is possible to implement everything, and the rest is just a matter of time and feasibility. Of course, if this doesn’t concern the limitations of the system, which we, as designers, will already know before the implementation begins;</li><li><strong>Independence.</strong> With great desire, you can become completely self-sufficient. This is already a question of necessity, but the fact that you can do something entirely yourself is motivating;</li><li><strong>Professional bonus.</strong> New experience in understanding your profession and a new evolutionary step in your career.</li></ul><p>What is the technical approach?</p><p>In this article, we will consider the first and, in my opinion, the most crucial aspect of working on a project — architecture.</p><p>Design is a dynamic environment. Setting the desired style and set of objects at the beginning will help maintain consistency.</p><p>Having decided on the design concept and already having some layout, we bring it to a structured form. It should not be forgotten that all elements should be named thoughtfully so that reading the name makes it immediately clear what this element is and its state. Yes, long names are often scary, but your colleagues will understand them, too.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/339/1*u4uPRNlh-wM6w49bMpJsxg.png" /><figcaption><em>A — Architecture.</em></figcaption></figure><p>Note that there are elements that will be reused in the project. Let’s take a closer look.</p><p>Does it make sense to constantly copy a group of elements for the Button object? And do we remember that this element has different states? Or does a teammate use the same button with a distinct shadow?</p><p>In this regard, we conclude that it is better to create such repeating elements not as a group of layers but as symbols. In our case, these are “Button” symbols in different states that are set in advance. Thus, the elements can be reused without fear that their style will differ.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/738/1*IqqvtFPcR2hu2Wx_lBTDmg.png" /><figcaption><em>Prepared button symbols in different states.</em></figcaption></figure><p>Do the same for the other elements that will be reused.</p><p>Now, we don’t have to search for the necessary object in already prepared layouts or duplicate a group of layers in a new layout. We have objects that are always available and even outside one file.</p><p>Let’s imagine a situation where you need to make an edit in one of the elements: change the font colour. It is enough to make changes in a symbol, and this style will be applied to all objects where it is used.</p><p>I recommend sharing this symbol library file if you work in a team. In this case, the team will always use the current elements.</p><p>What did we get in the end?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/513/1*ro0rEzEWXdvATx_PA01WiA.png" /><figcaption><em>Elements library. Lite version.</em></figcaption></figure><p>A file with the necessary elements and styles. And all that remains is to use it in your layouts like a Lego.</p><p>In this case, using a Git repository for version control and file sharing would be the cherry on top.</p><p>What we get:</p><ul><li>Any edits will be made as quickly as possible;</li><li>All layouts will be updated automatically, and all you have to do is check the result;</li><li>Style guides are collected in advance in a separate file;</li><li>Self-discipline in work.</li></ul><p>All this is only done through the use of project structuring. It’s not just a task, it’s a responsibility, a commitment to the quality and success of the project.</p><p>Creating, implementing, and scaling such a design system is not easy. But if you work through this stage at the beginning, expanding the functionality of your applications will be much easier and faster.</p><p>Implementing such a process involves a well-thought-out architecture at the initial stage of a product’s work.</p><p>What other benefits can technical knowledge bring to a designer? Let’s consider them in the following articles.</p><p>You can see the result on <a href="https://github.com/mnogosmyslov/StyleGuides-Library-v1.0-lite">GitHub</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cd16bb1bac97" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>