<?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 Olivia Nwose on Medium]]></title>
        <description><![CDATA[Stories by Olivia Nwose on Medium]]></description>
        <link>https://medium.com/@olivianwose?source=rss-4016c8cc9c61------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*qiIzIIy-N4MhCMtptEO7Uw@2x.jpeg</url>
            <title>Stories by Olivia Nwose on Medium</title>
            <link>https://medium.com/@olivianwose?source=rss-4016c8cc9c61------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 15:40:32 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@olivianwose/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[Refactoring UI.]]></title>
            <link>https://medium.com/@olivianwose/refactoring-ui-5a5664541ecc?source=rss-4016c8cc9c61------2</link>
            <guid isPermaLink="false">https://medium.com/p/5a5664541ecc</guid>
            <category><![CDATA[friends-of-figma]]></category>
            <category><![CDATA[fofuyo]]></category>
            <dc:creator><![CDATA[Olivia Nwose]]></dc:creator>
            <pubDate>Sun, 06 Mar 2022 16:40:16 GMT</pubDate>
            <atom:updated>2022-03-06T16:40:16.887Z</atom:updated>
            <content:encoded><![CDATA[<h4>First Three Chapters.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/208/1*uF7G8JookL7srxj7IPZkNw.jpeg" /></figure><h4>Starting From Scratch</h4><p>The best way to get discouraged while designing a new app idea is by trying to design the shell, that is the layout. Every app is composed of features, by the time you design a few features, you would have designed a great part of the app. At the very early stage of designing a new feature, it&#39;s okay to overlook certain minor details like shadows and typefaces, these features will come to play in time. If you have trouble doing this here’s a trick for you, first recreate the design using a thick sharpie.</p><p>It’s not very important to jump into adding colors, design on a grayscale. This will seem a bit challenging but you’ll end up with a clearer interface that’s easy to enhance color later.</p><p>When designing these features, at this stage don’t try to design how every feature should interact. Work in cycles, do not design everything at once, start with a simple design. Be a pessimist, yes exactly, pessimist. Expect that designing a new feature will be hard, do not try to implement a functionality that you aren’t ready to build. You might end up trying hard to implement the functionality, you’ll get frustrated and let go of designing the entire feature. Remember, having a simple feature is better than not having any at all.</p><p>While designing a product, choose a personality that best fits the product. Properties that help define a product’s personality are; Font choice, Color, Border-radius, Language. The best way to choose the best fitting personality for a product is to check put other sites used by the people you want to reach. The product design personality is the reason some product design seems playful while others seem official.</p><p>It gets quite difficult to choose when you have thousands of options to pick from. while designing a product, limit your choices, have a scale of colors or fonts you’ll likely use.</p><h4>Hierarchy Is Everything</h4><p>Visual hierarchy is how elements in an interface appear in relation to one another. Not all elements are equal, and you wouldn’t want your elements fighting for attention. Size isn’t everything, do not depend on only the font size to differentiate the elements according to importance or hierarchy. Font-weight and color go a long way in emphasizing content.</p><p>While designing emphasize to de-emphasize. Trying to emphasize a particular content in a group of contents? It&#39;s advisable to de-emphasize other contents in the group then add more emphasis on the selected one.</p><p>Without labels, we know that olivianwose@gmail.com is an email and $19.76 is a price. Do not hastily resort to labels, having a good hierarchy reduces the need for labels. Learn to combine labels and values, instead of “bedrooms : 3”, use “3 bedrooms”. Nevertheless, there are situations where labels should be emphasized, for example, a user checking out the specifications of a new phone will search for labels like screen width, etc.</p><p>When working with icons, we realize they take up a lot of surface area when placed beside a text that seems to appear emphasized. In such a case where we cant reduce the font-weight, it’s better we lower the contrast of the icon, giving it a softer color.</p><p>Every action on a page has a scale of importance, this is highly related to buttons. There are primary, secondary, and tertiary actions. A destructive action button such as delete and deactivate should be designed as big, red, and bold.</p><h4>Layout And Spacing</h4><p>One way to achieve a cleaned-up design is by giving the elements room to breathe. Let&#39;s see how to go about it, when designing an interface it&#39;s important to give more than enough white space between the elements, the gradually remove the spacing till it fits what you require. Do not forget dense UI have their place especially when you have a lot of elements you want to display at once.</p><p>Before starting the design of an interface, establish a spacing and sizing system. You don’t necessarily need to fit every content to full-width to correspond with elements like your nav-bar. Just as shouldn’t try to fill up spaces on a screen you shouldn’t try to force everything into a small space. If you are designing a responsive web application try shrinking the canvas to the mobile layout size.</p><p>Using a 12 column grid layout for alignment may seem alright at first, but the grid gives its contents a relative width that changes on different screen sizes, and there are situations where an element should have a fixed width, not relative width. Instead of giving the size of your elements based on a grid, it&#39;s better to give a max-width so they don’t get too large and they don’t shrink when the screen gets smaller.</p><p>It&#39;s okay to think that every element in an interface should be styled relative to one another, but the difference in screen sizes proves otherwise, it&#39;s, therefore, advisable to scale independently. The concept of scaling individually also applies to individual elements. Let go of the idea that everything should be scaled proportionally.</p><p>Avoid ambiguous spacing while designing, for example designing a form with different form fields, it&#39;s better if the spacing is between each pair of form fields and their labels. this applies both horizontally and vertically.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5a5664541ecc" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>