<?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 Andrew Ou on Medium]]></title>
        <description><![CDATA[Stories by Andrew Ou on Medium]]></description>
        <link>https://medium.com/@andrewou99?source=rss-99b84c89700a------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*sIiIhTpx6zgNtdVt.jpg</url>
            <title>Stories by Andrew Ou on Medium</title>
            <link>https://medium.com/@andrewou99?source=rss-99b84c89700a------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 01:45:10 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@andrewou99/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[The art in design you cannot ignore]]></title>
            <link>https://uxdesign.cc/the-art-in-design-you-cannot-ignore-a6e1076eb0cc?source=rss-99b84c89700a------2</link>
            <guid isPermaLink="false">https://medium.com/p/a6e1076eb0cc</guid>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[ui]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[art]]></category>
            <category><![CDATA[visual-design]]></category>
            <dc:creator><![CDATA[Andrew Ou]]></dc:creator>
            <pubDate>Wed, 25 Sep 2019 23:45:44 GMT</pubDate>
            <atom:updated>2019-12-22T21:45:34.343Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nPgJl2Pr67WtUtCYDlyfMQ.jpeg" /></figure><blockquote>“Art is about the artist, design is not about the designer.”</blockquote><p>The Long and Short —<a href="https://thelongandshort.ca/2017/05/30/design-art/#targetText=And%20so%20it%20is%20now,a%20basic%20standard%20of%20living."><em> Why Design is Not Art</em></a></p><blockquote>“Art is about personal expression. As such, it has intrinsic and independent value. The purpose and value of art is fully contained within the art itself.“</blockquote><p>Austin Knight — <a href="https://austinknight.com/writing/design-is-not-art"><em>Design is Not Art</em></a></p><blockquote>Art has no goal. Except when commissioned, art has no clear goal. Artists spawn pieces as a direct extension of their soul with no goal other than to be observed.</blockquote><p>Goran Peuc - <a href="https://artplusmarketing.com/@gpeuc?source=follow_footer--------------------------follow_footer-"><em>Design is Not Art</em></a></p><blockquote>“traditionally, artworks are intentionally endowed by their makers with properties, often sensory, having a significant degree of aesthetic interest”</blockquote><p>Stanford Encyclopedia of Philosophy —<em> </em><a href="https://plato.stanford.edu/index.html"><em>The Definition of Art</em></a></p><p>You have probably seen the “art vs. design” argument endless times by now. On the surface, it might seem clear that design is not art because it serves a purpose for a user, whereas art is about self-expression and the creator.</p><p>From my perspective, however, <strong>design is undeniably a form of art</strong>, but I am not going to explore this position fully here because once you understand the art in design, you will see why. If you are thinking this is just another post in the “art vs design” debate, it isn’t. The “art” I am talking about is <em>much</em> deeper. It has nothing to do with how pretty a design is. It has nothing to do with aesthetics. It is not something that is directly tangible, either.</p><p><strong>I will explain why there is an art in design you simply cannot ignore.</strong></p><p>Some people see design as art and some don’t. For those who do, it would help to understand the true meaning of art as there is often room for misinterpretation. Those who deny design is a form of art simply don’t understand art in its entirety and could benefit from reading what I have to share next.</p><h3><strong>What is art, really? It is about expression for all purposes.</strong></h3><p>When we hear the word “art”, we might think of paintings, drawings, music, photography, sculptures and dance. When we hear “artist”, we might think of a person, such an illustrator or painter who are talented in creating visual pieces with a much different purpose than design.</p><p><strong>However, at the foundational level, art has nothing to do with the forms or the artist</strong>. The “art” is not the painting we see or the music we hear.<strong> It cannot be grasped physically. </strong>In its purest form, it is quite abstract- art is simply self-expression <strong><em>without</em></strong> any attachment to purpose or form.</p><p>We might hear that art is self-expression for the sake of expression, that it serves no purpose other than to express, or that it is purely meant for the artist and meant to evoke subjective emotions. These are incomplete and incorrect definitions since they attempt to limit art.<strong> I’d like to re-establish that since art has no limitations; it is capable of assuming all forms and definitions, even if it is an expression for a purpose, and even if the expression is for others, not just the artist</strong>. One could create art for the sake of expression, but one could also create art with the intention of communicating a specific message. Both are valid, but note that the latter strives to target an audience to serve a purpose, much like design.</p><figure><img alt="A giant wave composed of plastic pieces instead of water" src="https://cdn-images-1.medium.com/max/1000/1*61RBqCuDIJHJxiV-uSckQg.jpeg" /><figcaption>The iconic “<em>Great Wave of Kanagawa” recomposed using plastic. It was the artist’s </em><strong><em>intent to communicate and raise awareness of plastic pollution to an audience</em></strong><em>, which makes this a design piece, even though many would consider this “art”.</em></figcaption></figure><p><em>Simply put, art is about expression without limitations. Art can serve all purposes, even the purpose of meeting a specific goal.</em></p><h3><strong>A prime example of art in design</strong></h3><p>In 2008, the paradigm for the placement of a refresh button in mobile apps was to put them somewhere on the screen. Developers would often try to find a place to squeeze them in, and they would often end up on the bottom toolbar. Thousands of apps and mobile developers followed this convention. Even Apple had its own established guidelines for a refresh button.</p><p>Like many others, <a href="https://en.wikipedia.org/wiki/Loren_Brichter">Loren Brichter</a>, the developer of the Tweetie app, tried to fit the refresh button on the toolbar. However, he felt that the toolbar should be reserved for more important action items, so he decided to think differently. He brainstormed different ideas, until he came across the “pull-to-refresh” gesture. At that time, this gesture did not exist. But when he created it, it introduced a new convention for the refresh function, which Twitter later acquired and patented. This creation inadvertently evolved the design convention.</p><p>As there was no other way, he created his own way<em>. </em>Brichter thought differently, and decided to express his vision of how to provide the refresh function against what thousands of mobile apps were doing. It even contradicted the established iOS platform convention.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/885/1*wdnOqNc1eYK0QIZsWfcgBw.png" /></figure><p><strong>It was an expression of a personal vision. <em>This </em>is a prime illustration of art at its core.</strong></p><h3><strong>So why is art Important in design?</strong></h3><blockquote>Design evolves because of art.</blockquote><p>Design can only evolve through what is living — our thoughts, ideas, and expressions as living beings. Design trends and new patterns become reality because they begin with <em>one person’s</em> expression that attempts do things differently, beyond what is already established. Without art in design, design becomes a limited strict set of mechanical procedures which does not evolve.</p><p>Art is important because without it we would not be able to exercise our design intuition, our gut instincts as designers. Without art, we must only do exactly what is asked, give our users exactly what they say they want, and throw out all ideas and everything which contradicts what is established. We can practice only what is known, and never explore any other possibilities.</p><p>However, we know this is not reality. There are hundreds of thousands of designers in the world. We come from different backgrounds, have different strengths and weaknesses, and think and express ourselves differently. This is the flavor which evolves the design field, which gives our practice new ideas and meanings.</p><p><strong>As designers, it’s important to have your own expression</strong> instead of blindly following traditions and existing patterns and processes just because that’s what everyone else is doing. Just because things are done a certain way, doesn’t mean that’s the best or the only way. Just because something is established doesn’t mean it’s right.</p><p>For example, when designers are creating a mobile app, they tend to believe they need to follow native Android or iOS patterns because they are platform conventions and it would be wrong to deviate from them. I find this thinking to be incomplete and limiting, and explain in another article <a href="https://uxplanet.org/you-dont-always-need-to-follow-native-android-or-ios-ui-patterns-when-designing-an-app-2a361a21c342"><em>why you don’t always need to</em></a>. This is my expression and how I lead the thinking in the companies I work with.</p><blockquote>The art in design allows us to do things differently: to go above and beyond, to take risks and make tough decisions where data and precedents don’t exist. It allows us to devise strategies, imagine unconventional ideas and new patterns and processes, and ultimately express things the way we believe we should. This is also what separates an exceptional designer from an average one.</blockquote><blockquote><strong>This is the art in us. And this is the art in design you cannot ignore.</strong></blockquote><p>Andrew Ou is a UX Designer and author of <a href="https://amzn.to/34SUoxb"><em>The Tao of Design and User Experience</em></a>. His philosophy on UX design stems from a unique perspective, grounded in martial arts and Taoism. Follow him if you would like to read what he has to share.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a6e1076eb0cc" width="1" height="1" alt=""><hr><p><a href="https://uxdesign.cc/the-art-in-design-you-cannot-ignore-a6e1076eb0cc">The art in design you cannot ignore</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[You don’t always need to follow native Android or iOS UI patterns when designing an app]]></title>
            <link>https://uxplanet.org/you-dont-always-need-to-follow-native-android-or-ios-ui-patterns-when-designing-an-app-2a361a21c342?source=rss-99b84c89700a------2</link>
            <guid isPermaLink="false">https://medium.com/p/2a361a21c342</guid>
            <category><![CDATA[ui-design]]></category>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[mobile-app-development]]></category>
            <category><![CDATA[user-experience]]></category>
            <dc:creator><![CDATA[Andrew Ou]]></dc:creator>
            <pubDate>Thu, 02 May 2019 14:27:25 GMT</pubDate>
            <atom:updated>2020-07-18T06:36:49.086Z</atom:updated>
            <content:encoded><![CDATA[<h3>You don’t always need to follow native Android or iOS patterns when designing an app</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Zj_xVGl_brd5FMzwP4qdug.png" /></figure><p>When we design an app, one of our major tendencies and natural processes is to follow the native design patterns of Android and iOS. Following platform conventions is a practical approach, and definitely seems like quite a sensible one. Some job applications requires us to be familiar with the separate Android and iOS mobile patterns. And every existing content or blog that writes about this topic will <strong>only </strong>recite, as it is, what appears to be the difference between Android and iOS according to their platform guidelines. This causes many to think that it is the right way of doing things. However, it is a major problem.</p><p>I’d first like to point out some of the key UI differences between Android and iOS, <strong>but more importantly, share why it is limiting to think we need to closely follow native UI patterns when designing an app.</strong></p><blockquote><strong>The truth is, you don’t always need to. I’ll explain why.</strong></blockquote><h3>The basic differences between iOS and Android</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/919/1*7JgFWWcD_pfk-aas6b6jgg.png" /></figure><p>First, we can all agree that one of the most striking differences between Android and iOS is that iOS uses navigation at the bottom of the screen, while Android uses tabs, often supplemented with swipe, to navigate. Android has its Material Design language, while iOS has its Human Interface guidelines.</p><p>Beyond that, there are other differences such as interaction patterns and visual styling of components. iOS titles tend to be centered whereas Android titles are placed on the left. Visual components such as lists, radio buttons, etc. may have their own visual styles.</p><h3>The problem with the concept of the “Android” style and the “iOS” style</h3><p>Unfortunately, this separation of styles is where the problem begins. It influences us to think that there is a correct “Android” or “iOS” way to design and use an app.</p><p>A simple checkbox is widely understood on a website. But in native applications, we begin to emphasize the correct way to display it according to Android or iOS guidelines. When this happens, simple decisions become quite trivial and arbitrary.</p><p>This thinking ultimately leads us to create a separation between iOS and Android users, rather than simply seeing them all as human beings.</p><p>At the extreme end of this mindset, it limits our design, our approach, and our understanding by assuming that we should and must<strong> </strong>solve the problems we encounter in a certain way; that is, by following platform conventions.</p><h3>The true difference between iOS and Android</h3><p>Let’s for a moment shift our thinking to <em>eliminate</em> concepts of “iOS” and “Android” design patterns, and simply think of our users as “smartphone users”, or simply as human beings using palm-sized touchscreen device.</p><p>To design an interface for such a device:</p><ul><li>We should place navigation at the bottom of the screen, where it is easy for the thumb to reach. If we want to place navigation at the top, we should supplement it with swiping for better accessibility.</li><li>Buttons should be finger sized.</li><li>Back buttons should appear at the top left corner.</li><li>A checkbox (called a switch in iOS) should simply look and behave like a checkbox.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/444/1*sc73UulJsquM2rPvtGkALg.png" /></figure><p>Note that while the checkbox on the left might be wrong according to the Android or iOS defined pattern, it cannot objectively be wrong because it is still a checkbox.<em> It is universally understood and used as a control which indicates an on/off state.</em></p><p>So far, we are making no reference to any platform-specific convention. <strong>Rather, this approach generates a design that simply serves as a palm-sized digital interface for a human being</strong>. Regardless of whether we are an Android or iOS user, we have no more than two hands and ten fingers, and interact with the device by tapping it or swiping one way or another. We understand buttons, icons, and popups on websites, so why are there sudden distinctions when it comes to native applications?</p><p>If we understand and approach design from this perspective, we are simply designing for human interaction, rather than trying to satisfy the illusion of style, to get to the truth.</p><blockquote><strong>This is simply the human concept without the attachment of “styles”. If it works for a human being, then it simply cannot be wrong, even if it doesn’t follow “established” patterns. </strong>When you understand this perspective, then the truth becomes obvious — <strong>there is no difference.</strong></blockquote><p>There is no need to be fixated and misled by the ideology that we need to follow “established” patterns, or to frown upon those who deviate from what is established. There are hundreds of thousands of responsive websites designed for mobile use which do not distinguish between iOS and Android visitors. They simply appear as palm-sized digital interfaces.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/0*PDwog8UGybaDs66L" /><figcaption>With the platform based approach, we express the solution through a platform specific convention. With the human approach, we simply express the solution on a palm-sized touch screen device.</figcaption></figure><h3>Proof</h3><p>With hundreds of millions of users, apps like YouTube, Airbnb, and more have streamlined this approach. They have defined their own style which does not favor a particular “Android” or “iOS” style. Thousands of game apps also do not distinguish between “Android” or “iOS”- they simply have their own stylized UI wrapped in a smartphone.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/0*oitLI1SLMcHpfPc5" /></figure><p>In March 2016, Google added bottom navigation to their Material Design guidelines. Before this, one might have argued that bottom navigation is an iOS pattern, which does not belong on Android. However, from a human perspective, it simply works. This addition closes one of the major gaps in the differences we observed between iOS and Android. What might have been deemed “incorrect” or “unconventional” is now “correct”.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/0*aWuTeJGcsgfVtdoO" /></figure><h3>Major advantages of using one design</h3><p>Using one design for both platforms has some major advantages, one of them being that it strongly favours efficiency as there is no need to maintain two separate designs. When making design choices, we also don’t get caught up believing things should be done the “Android” way or the “iOS” way for the sake of satisfying conventions.</p><p>We may even be able to use a single code base, eliminating the need for separate “Android” or “iOS” development and developers.</p><p>Creating a uniform design across all mobile devices is also a key point in maintaining a <strong>consistent experience</strong> for all users of all devices.</p><h3>The simple truth</h3><p>With thousands of apps in the app stores, and even the popular ones with hundreds of millions of users all doing different things, which, then, is the correct way to design an app?</p><blockquote><strong>The truth is that there is simply no right or wrong.</strong></blockquote><p><em>All solutions are valid if they work</em>. The only real mistake is when we become so fixated on emphasizing and following what we think of as the “correct” and “established” way that we become narrow and limited.</p><h3>So when should we use native? When should we use a uniform design?</h3><p>As a simple guideline, we could follow native Android or iOS conventions only when we are creating an app for a single platform.</p><p>We should consider using one design if budget is limited, and we want to emphasize efficiency, by using one codebase to produce both Android and iOS versions of a single app.</p><p><strong>These are guidelines, not hard rules</strong>. Factors such as technological limitations, performance, budget, resources, and the expectations of the target audience should also be considered when making design decisions.</p><blockquote>The important takeaway is that we can zoom out and see the big picture, that we are designing a <strong>palm-sized interface</strong> <strong>for human beings to use</strong>, without the illusions of platform conventions and a separation between “iOS users” and “Android users”.</blockquote><p>Andrew Ou is a UX Designer and author of <a href="https://amzn.to/34SUoxb"><em>The Tao of Design and User Experience: The Best Experience is No Experience</em></a>. His philosophies on UX design stems from a unique perspective- Martial arts and Taoism. Continue reading to see how he uses an example.</p><h3>An analogy using martial arts</h3><p>In martial arts, there are many different styles and forms of fighting, such as Karate, Boxing, Judo, etc. Each style has its own set of doctrine and principles. Sometimes, what is “right” in one system may appear to be “wrong” in another.</p><p>Similarly, what is “right” on Android may be “wrong” according to iOS principles.</p><p>If we throw away the concept of styles and adopt the <strong>human perspective</strong>, then in reality, there is no such thing as a Japanese (Karate, Judo) or a Western (Boxing) way of kicking and punching. A punch is a punch, and a kick is a kick. <strong>Fundamentally, they are just human movements. When you understand this, styles become superficial.</strong></p><p>In the same way, there is no such thing as an “Android” way or an “iOS” way of using a phone. We are all just human beings using palm-sized digital interfaces.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fupscri.be%2Fb3e808%3Fas_embed%3Dtrue&amp;dntp=1&amp;display_name=Upscribe&amp;url=https%3A%2F%2Fupscri.be%2Fb3e808%2F&amp;image=http%3A%2F%2Fapi.screenshotlayer.com%2Fapi%2Fcapture%3Faccess_key%3Dfe59908dad3baab69ffab249a2224b03%26viewport%3D1024x612%26width%3D1000%26url%3Dhttps%253A%252F%252Fupscri.be%252Fb3e808%253Fscreenshot&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=upscri" width="800" height="400" frameborder="0" scrolling="no"><a href="https://medium.com/media/96d08ab34921bdd17986cb5c0396842f/href">https://medium.com/media/96d08ab34921bdd17986cb5c0396842f/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2a361a21c342" width="1" height="1" alt=""><hr><p><a href="https://uxplanet.org/you-dont-always-need-to-follow-native-android-or-ios-ui-patterns-when-designing-an-app-2a361a21c342">You don’t always need to follow native Android or iOS UI patterns when designing an app</a> was originally published in <a href="https://uxplanet.org/">UX Planet</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>