<?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 Saniya Mazmanova on Medium]]></title>
        <description><![CDATA[Stories by Saniya Mazmanova on Medium]]></description>
        <link>https://medium.com/@saniyamazman?source=rss-d326a8f5ddc9------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*RuStwJfBtf3mAaddnwLdoQ.jpeg</url>
            <title>Stories by Saniya Mazmanova on Medium</title>
            <link>https://medium.com/@saniyamazman?source=rss-d326a8f5ddc9------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Mon, 16 Nov 2026 14:36:54 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@saniyamazman/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[Google App: Small Change — Big Difference]]></title>
            <link>https://medium.com/nyc-design/google-app-small-change-big-difference-45e7178ccff3?source=rss-d326a8f5ddc9------2</link>
            <guid isPermaLink="false">https://medium.com/p/45e7178ccff3</guid>
            <category><![CDATA[new-york]]></category>
            <category><![CDATA[google]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[mobile]]></category>
            <category><![CDATA[redesign]]></category>
            <dc:creator><![CDATA[Saniya Mazmanova]]></dc:creator>
            <pubDate>Mon, 06 Aug 2018 11:13:22 GMT</pubDate>
            <atom:updated>2018-09-21T05:49:01.285Z</atom:updated>
            <content:encoded><![CDATA[<p>The Google app is my all-time favorite because it’s clean, fast, and has all the information I need. However, I came across this amazing article about <a href="https://medium.com/@Draward/mobile-reachability-rules-of-thumb-ce37dd0cd3ad"><strong>reachability</strong></a><strong> </strong>and it inspired me to find ways to improve the app’s experience.</p><p>Currently, the Google app has a search engine in the middle of the page.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/833/1*c5dvHUc6uNwdp94aiKU4Og.png" /></figure><p>Great UI, don’t you agree?</p><p>If we look at the reachability map, the position of the current search engine on the app is not at the <em>easy-to-reach</em> area. I tested out reachability on the iPhone x and people have a hard time reaching the search engine, especially those with small thumbs.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lmGdCJVQ9Y2-SkvBvNsXbw.png" /><figcaption><a href="https://medium.com/@Draward/mobile-reachability-rules-of-thumb-ce37dd0cd3ad">https://medium.com/@Draward/mobile-reachability-rules-of-thumb-ce37dd0cd3ad</a></figcaption></figure><p>The simple solution?</p><p>Move the search engine down to where users can achieve reachability with the least amount of effort (the green area).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/833/1*gWbF-5zvXAgNZuOCsgo2bw.png" /><figcaption>Redesign by yours truly. Originally I had the icons on both screens but a <a href="http://manobarkovics.com/">good friend of mine</a>, who is also a UX/UI Designer, pointed out that having icons on both screens is a little repetitive. I found this to be a valid reason to remove the icons from the second search page.</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/352/1*gddnPd52GEfEdXvkH7pFkA.gif" /></figure><p>Let’s test for reachability, shall we?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5CUibNXNOo2S3NQxuAw2Bg.png" /></figure><p><strong>As you can see, the search bar is almost 100% in the most reachable area of the screen compared to only about 45%.</strong></p><p>Another small change that I made was moving the search icons to the home page to speed up the search process. Even better, it could be personalized based on user’s search history. As a book addict, I would want to always see a book icon on that list.</p><p>Oh, and also, have you noticed that the text color inside the search engine is a darker grey? Well, there’s a thing called accessibility which I am a big fan of.</p><p>Yes, I know there is a reachability option on the iPhones, but this small effort on Google’s side will make the lives of millions much easy. I am also aware that there are other <a href="https://uxdesign.cc/what-every-product-designer-should-take-away-from-lyfts-new-ui-742c9668b067">applications</a> that follow this method and honestly, that makes me happy. I hope that we can continue to look for inspiration and opportunities in the technologies that we use in our everyday lives and speak out to make a difference.</p><p>Clap once if you liked this article 😀</p><ul><li><a href="https://medium.com/@Draward/mobile-reachability-rules-of-thumb-ce37dd0cd3ad">Mobile Reachability. Rules of Thumb</a></li><li><a href="https://uxdesign.cc/what-every-product-designer-should-take-away-from-lyfts-new-ui-742c9668b067">What every product designer should take away from Lyft’s new UI</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=45e7178ccff3" width="1" height="1" alt=""><hr><p><a href="https://medium.com/nyc-design/google-app-small-change-big-difference-45e7178ccff3">Google App: Small Change — Big Difference</a> was originally published in <a href="https://medium.com/nyc-design">NYC Design</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Designers Who Code (AKA Unicorns)]]></title>
            <link>https://medium.com/nyc-design/designers-who-code-aka-unicorns-38b5256fd06f?source=rss-d326a8f5ddc9------2</link>
            <guid isPermaLink="false">https://medium.com/p/38b5256fd06f</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[react]]></category>
            <category><![CDATA[developer]]></category>
            <category><![CDATA[code]]></category>
            <category><![CDATA[new-york]]></category>
            <dc:creator><![CDATA[Saniya Mazmanova]]></dc:creator>
            <pubDate>Thu, 17 May 2018 18:26:56 GMT</pubDate>
            <atom:updated>2018-08-08T06:55:26.992Z</atom:updated>
            <content:encoded><![CDATA[<p>My very first UX/UI project was designing and building a portfolio using paper, pencil, HTML, CSS, and JavaScript. I loved playing around with the code to create animations, pretty visuals, and link one page to another and another. I assumed that a good designer should be able to produce his/her own code. However, that’s not what I heard from other designers. When I asked them if they code, most responded with a “no” or “I know how to, but I’m not required to do it”. Of course, being new in the field, I did what most other designers did: started using prototyping tools such as Sketch, Figma, Illustrator, and InVision to produce designs. But I found myself getting frustrated with these tools, not because they’re bad but because I expected something more.</p><p>In this article, I will tell you why I think every designer should get their hands dirty with code. I don’t mean designers should take over the role of a front-end developer, but they should understand the fundamental principles of programming and be able to contribute to the code.</p><h3>The History and The Gap</h3><p>When the web was first introduced, user-centered design was not a part of the revolution. It was up to the developers to “design” layouts and components. And the outcome was quite painful, take a look at Yahoo’s very first design. The page is cluttered with links, low-quality visuals, and does not have an appealing look.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/460/1*jq3FVsg50DCgHOjDcxtgzA.png" /><figcaption><em>Image taken from </em><a href="http://www.hughmorgan.net/"><em>http://www.hughmorgan.net/</em></a></figcaption></figure><p>Over the past couple decades, as more people began to embed technology into their everyday lives, user-centered design has become a big deal leading to it becoming a role of its own. As both roles became equally important, the communication levels have declined, creating a communication gap between design and development.</p><h3>The Communication Gap</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/734/1*gZJwfKjT2P2jRrbjrT_VfQ.png" /></figure><p>Allow me to explain the communication gap as illustrated by me (the original idea for this diagram came from Jamie Snider who teaches Design Thinking at UW Seattle): on the left side, we have the design stage that goes from concept to creation (research, UX design, UI design, analysis). On the right side, we have the development stage that transforms the creation from design into reality (front-end and back-end development). The gap on the left is formed by the lack of communication, understanding, and empathy between designers and developers. This creates a shaky foundation for the product. The gap leads to a shortfall, affecting one or more of the following: the functionality of the product, the look of the product, requirements, timeline, and/or budget.</p><h3>React to the Rescue</h3><p>React can be the most effective way to close the communication gap between the design and development stages. <strong><em>But what is React?</em></strong></p><p>It is a JavaScript library to build User Interfaces. It is fully component-based, meaning you create your reusable components and then compose them into a web page. React is written in JSX syntax, which is fairly similar to JavaScript. Don’t want to learn JSX? No problem. You could use Babel to transform JavaScript code to JSX. Now the interesting part of React: every component is created and styled in the render() method (inside the JSX file) using a syntax very much like HTML and CSS. Take a look at the code below.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/408/1*zhTyvlZvBh1lBQsJnKClLg.png" /><figcaption>React code</figcaption></figure><p>Basic styling syntax is in the middle of some complicated code that takes care of the functionality of the software. And if you don’t know much about HTML and CSS, just know that they are the <em>easiest</em> languages to learn in the development world. <strong>Which means, there is no reason <em>anyone</em> shouldn’t be able to code in React.</strong></p><h3><strong>How React Can Help</strong></h3><p><strong><em>Terminology</em></strong></p><p>It’s absolutely critical for designers and developers to work side-by-side and have a good means of communication, meaning that both parties understand each other and get things done. In order to close the communication gap, designers must be able to speak code and developers must be able to speak design, which is exactly what React enforces: it adds styling syntax (design) among functionality syntax (development). It creates a canvas where designers and developers can add on to in order to paint the whole picture.</p><blockquote>“Design and development are neatly convergent — everyone wins when they understand more of both.” — Danilo Campos</blockquote><p><strong><em>Know What’s Possible and What’s Not</em></strong></p><p>This is a big issue in the design world. We creatives can come up with wild solutions without considering the difficulties that it will impose on the developers. Knowing what can and cannot be accomplished with code, and if the benefits are greater than the costs are important when working on a tight budget and timeframe. It could also make or break the relationship between designers and developers. Instead of forcing developers to build a specific design, designers can show that it is possible or learn that it is not based on their attempt to code the design in a tool like React.</p><p>Also, many developers like to stick to what they are already familiar with. You don’t want your flows and designs disregarded because a developer wants to use a specific framework that cannot support your design decisions. When you’re already familiar with the possibilities of the framework your developers use, there are fewer limitations. Even Alex Kotliarskiy, who works for the React Native team at Facebook, says that user experience should not be compromised by the framework that is chosen to work with. There are dozens of frameworks with custom-designed components made specifically for React and he encourages people to explore them.</p><p><strong><em>Step Up Your Game (not React specific)</em></strong></p><p>Tools such as Sketch, Figma, and InVision are all great (I use them on a daily basis) but they have their limitations and challenges. Without creating components on Sketch or Figma, a designer will have a very hard time updating the color of a single button on every screen. If you make changes to the layout of a page, then you must move all the hotspots to new locations on InVision. Want some animations? Look for another app that will do that. Responsive design? Good luck.</p><p>With code, you can style a button in one place, change the layout as you desire, and animate anything. You are able to see your flow and design in action and make changes as you discover opportunities.</p><h3>Conclusion</h3><blockquote>“None of us, including me, ever do great things. But we can all do small things, with great love, and together we can do something wonderful.” — Mother Teresa</blockquote><p>Like I said before, I am not asking designers to master front-end development. However, being capable of understanding, communicating, and contributing to code can help the product become more successful. Also, it will create a more enjoyable and effective work atmosphere for both designers and developers. Not to mention, you will definitely stand out as a designer. I’d love to hear your opinion on this topic! Feel free to reach me at <strong>mazman94.sm@gmail.com</strong> and we can have a conversation.</p><p><strong><em>I’d like to give special thanks to Bob Boiko.</em></strong></p><h3>References</h3><p>Campos, Danilo. “Why Don’t More Designers Code?” <em>Quora</em>, 11 July 2012, <a href="http://www.quora.com/Software-Product-Design/Why-dont-more-designers-code/answer/Danilo-Campos?share=1&amp;srid=8P8.">www.quora.com/Software-Product-Design/Why-dont-more-designers-code/answer/Danilo-Campos?share=1&amp;srid=8P8.</a></p><p>Kotliarskyi, Alex, director. <em>Building Stellar Mobile UX With React Native</em>. YouTube, 30 July 2017, <a href="http://www.youtube.com/watch?v=ssXB9RMTpTs.">www.youtube.com/watch?v=ssXB9RMTpTs.</a></p><p>Nouvel, Sergio. “Every UI Designer Needs to Learn React. Here’s Why — Continuum.” <em>Continuum</em>, Continuum, 22 Sept. 2017, blog.continuum.cl/every-ui-designer-needs-to-learn-react-heres-why-f2b8c2ff2c86.</p><p>Treder, Marcin. “Should Designers Code?” <em>Studio by UXPin</em>, 1 Feb. 2017, <a href="http://www.uxpin.com/studio/blog/should-designers-code/">www.uxpin.com/studio/blog/should-designers-code/.</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=38b5256fd06f" width="1" height="1" alt=""><hr><p><a href="https://medium.com/nyc-design/designers-who-code-aka-unicorns-38b5256fd06f">Designers Who Code (AKA Unicorns)</a> was originally published in <a href="https://medium.com/nyc-design">NYC Design</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>