<?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 Aaron Cheng on Medium]]></title>
        <description><![CDATA[Stories by Aaron Cheng on Medium]]></description>
        <link>https://medium.com/@aaroncheng?source=rss-33ae012bf377------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*SjotY7jKVZPF9UDW.jpg</url>
            <title>Stories by Aaron Cheng on Medium</title>
            <link>https://medium.com/@aaroncheng?source=rss-33ae012bf377------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Mon, 16 Nov 2026 23:29:58 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@aaroncheng/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[Mobile UI Design for One-handed Use]]></title>
            <link>https://medium.com/@aaroncheng/design-for-one-handed-use-a3b28c986a89?source=rss-33ae012bf377------2</link>
            <guid isPermaLink="false">https://medium.com/p/a3b28c986a89</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Aaron Cheng]]></dc:creator>
            <pubDate>Wed, 13 Jul 2016 17:55:44 GMT</pubDate>
            <atom:updated>2016-08-01T19:19:23.469Z</atom:updated>
            <content:encoded><![CDATA[<p>I remember before the smart phone was invented, I could use only one hand to type text messages and make calls. But now I have to use two hands to finish some tasks on my iPhone. The main reason is that the screen gets bigger and it is hard to reach the upper part. It sounds like an obvious problem, but why do we still insist putting those buttons at those awkward locations? I guess the answer from most people is ‘because everybody is doing that.‘ Well, I think now it is time to break the rule and start doing the right thing. I happen to be redesigning an e-commerce app recently and it is the perfect opportunity to explore the possibility of creating a one-handed use design pattern for mobile apps.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Xxl2TG3TzYHyOIJ3f2EPNA.png" /></figure><h4>Identify the ‘safe zone‘</h4><p>Before we jump into the design, we need to figure out the ‘safe zone‘ on the screen. I use iPhone 6 for the test. Because if the design works on iPhone 6 and it should work better on smaller screens. Those smart phones bigger than iPhone 6 are designed for two-handed use and there is no need to worry about them.</p><p>The green color indicates the ‘safe zone‘ in which it is easy to move my thumb around. Within the blue area, it gets a little bit harder, but I am still able to reach any spot. The red zone is the area that is impossible for me to reach without moving my other fingers. So in our design, we should put all the buttons and other interactive elements within the green and blue area and stay away from the red zone.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DQPgBSt8eL66RBFyjjUWgw.png" /></figure><h4>Find the problems</h4><p>Now let’s take a look at some examples and find the problems we are gonna solve. Basically, there are 4 types of interactive elements often being used in the red zone: List of items, Back button, Sub navigation and Action buttons.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*S6hXcCJUymUCzYRI21ESeg.png" /></figure><h4>Solution for ‘list of items’: Make the first item bigger or add informative content</h4><p>List items stack from top to bottom. To avoid placing them in the red zone, we need to push them down. There are 2 ways of doing this without leaving an empty space: 1. Make the first item big enough so the bottom part can reach the safe zone. In the redesigned ‘Me‘ page, the user’s avatar is enlarged and the user can click its bottom part to edit the profile image. 2. Add informative content to the top. In the new shopping cart design, I moved shipping and tax fees on the top of the page to push the first item to the safe zone. However, you can notice that only the bottom part of the item is in the safe zone, to make it easy for users to click the ‘X‘ icon, I move it to the bottom and change it to ‘REMOVE‘.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zwcTZMkYmE4LUO0hMzEUJg.png" /></figure><h4>Solution for ‘Back button’: Popover window</h4><p>Back button is one of the most used buttons on mobile app. Android phone even makes it a fixed physical key. However, it is placed at the top-left corner of the screen in iOS, which is extremely hard to reach. The idea of the solution comes from the popover window on desktop: to close the popover, we tend to click anywhere outside the popover other than the close button. In the new detail page design, I put the detail info in a big popover, which is actually the same size as the old design, but the dimmed status bar and tab bar makes it look like floating above the previous page.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0uAFCVbXeYii0gNMVCH2TA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*w6QFYlVWlIQ6flqLGYjHHw.png" /><figcaption>Flow</figcaption></figure><h4>Solution for ‘Sub navigation’: Enable left-right swiping</h4><p>It is relatively easy to solve this problem. All we need to do is to enable users swiping left and right to switch among different tabs. In the new ‘Discovery’ design, I changed the style of the sub navigation to make it look like more swipeable.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3H14lcdXP4OXAjHN9xYY1A.png" /></figure><h4>Solution for ‘Action buttons’: Move everything to the tab bar</h4><p>Back button is one of the most used buttons on mobile app. Android phone even makes it a fixed physical key. However, it is placed at the top-left corner of the screen in iOS, which is extremely hard to reach. The idea of the solution comes from the popover window on desktop: to close the popover, we tend to click anywhere outside the popover other than the close button. In the new detail page design, I put the detail info in a big popover, which is actually the same size as the old design, but the dimmed status bar and tab bar makes it look like floating above the previous page.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*EocmYBE0xBY6vOYaEwXQrw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*iXfROhByo6kuAu0mk14umw.png" /><figcaption>Flow</figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a3b28c986a89" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[‘My Objects’: A Study of Advanced Searching and Filtering]]></title>
            <link>https://medium.com/@aaroncheng/my-objects-a-study-of-advanced-searching-and-filtering-ed097fe0510a?source=rss-33ae012bf377------2</link>
            <guid isPermaLink="false">https://medium.com/p/ed097fe0510a</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[user-experience]]></category>
            <dc:creator><![CDATA[Aaron Cheng]]></dc:creator>
            <pubDate>Wed, 13 Jul 2016 17:34:03 GMT</pubDate>
            <atom:updated>2016-07-13T17:36:48.941Z</atom:updated>
            <content:encoded><![CDATA[<p>‘My Object‘ is a new feature we recently added to the Striim’s platform. It is essentially a list of different types of objects. However, the challenging part is the design of the filter and search functionality. During the process, I came up with 3 different options and it is quite interesting to see how the design evolved.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OCz20-7bpIkwudQEiyzqNQ.png" /></figure><p>Before I start to design anything, the first thing I do is to extract all the related objects and study their relationship and properties. At Striim, there are 3 types of objects: Namespace, App and Components. ‘Namespace’ acts like a folder used to organize ‘Apps’ and ‘Component’, which can only be filtered by ‘Object Type‘. ‘App‘ is a data pipeline that consists of different ‘Components‘. It can be filtered by both ‘Object Type ‘ and ‘Namespace‘. There are 7 types of ‘Components‘: Source, Cache, Window, CQ, WactionStore, Alert and Type. All ‘Components’ can be filtered by ‘Object Type‘, ‘Namespace‘ or ‘App‘.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/443/1*uTcbOnpmWffpyllWGgxxkA.png" /></figure><p>To measure the functionality of the design, I created 3 user tasks from simple to complex:</p><p><strong>Single filter</strong>: Show all the Caches with the keyword ‘merchant‘.</p><p><strong>Multiple filters</strong>: Show all the Caches under ‘myNameSpace‘ with the keyword ‘merchant‘.</p><p><strong>Multiple criteria</strong>: Show all the Caches under ‘myNameSpace‘ with the keyword ‘merchant‘ and all the Sources under any Namespace.</p><h4>Option 1: Single filter</h4><p>Since the ‘Object Type‘ is the only filter that can be applied to all objects, the idea of Option 1 is to emphasize this filter and make it really easy to use. So I lists all the object types on top, which allows users quickly filtering any object type by one simple click. But this design is limited to single filter and users can’t filter objects by ‘Namespace‘ or ‘App‘.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XgHC1uEE9i6cCWmlu5JvWw.png" /></figure><h4>Option 2: Multiple filters</h4><p>In Option 2, I replaced those object icons with 3 filter buttons below the search box. Users can create multiple filters by clicking any button and multi-select the options in the dropdown list. However, this design still has 2 major problems. The first one is those filters are all in ‘AND‘ relation, so there is no way to do something like “Show all the Caches under ‘myNameSpace‘ and all the Sources under any Namespace“. The second problem is the interface only shows the number of the applied filters.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6XhyXzr6n7GAvWph2Gs5AA.png" /></figure><h4>Option 3: Multiple criteria</h4><p>Filter with multiple criteria requires complicated interactions. What Option 2 does is merely a single criteria. To enable multiple-criteria filtering based on Option 2’s design logic, I will have to provide an ‘Add‘ button somewhere and ask users to repeat the flow every time they add a new criteria. The process works but the problem is those filters can potentially take a big chunk of space and users will see less objects in the list.</p><p>To solve the problem, I integrated the filter with the search bar. (If you think about it, search is actually a type of filter, so it makes perfect sense to put them together!) When users click the search bar, a drop down will list 3 categories of filter and then users can follow the similar process in Option 2 to keep adding more ‘AND’ filters until they hit ‘Enter‘, which will end the current criteria and put it under the search bar. Users can add more ‘OR‘ criteria by repeating the previous process. Compared with the other 2 options, Option 3 solves the most complicated problem with the simplest UI — a search bar.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MpE2SKvR-eqKL__y_RhR0Q.png" /></figure><p>If you wanna see more my works, please visit my website at <a href="http://www.chengfolio.com/">www.chengfolio.com</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ed097fe0510a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Shopping Cart UI Design]]></title>
            <link>https://medium.com/@aaroncheng/shopping-cart-ui-design-6c739fcab6ef?source=rss-33ae012bf377------2</link>
            <guid isPermaLink="false">https://medium.com/p/6c739fcab6ef</guid>
            <category><![CDATA[user-interface]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[shopping]]></category>
            <dc:creator><![CDATA[Aaron Cheng]]></dc:creator>
            <pubDate>Fri, 31 Jul 2015 03:37:06 GMT</pubDate>
            <atom:updated>2015-07-31T17:52:03.357Z</atom:updated>
            <content:encoded><![CDATA[<p>Recently I have been revamping the design of Bieyang’s mobile app. As an e-commerce application, the shopping cart is probably one of the most important pages to our users and it becomes critical for us to improve the user experience.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/352/1*hU99YNm-d3qCVO71nfGiDQ.png" /><figcaption>Bieyang’s shopping cart design</figcaption></figure><p>Checkout is a long and complicated flow and I won’t cover everything in this article. Today I will only focus on the shopping cart page. Our goal was to simplify all the various inputs based on our users’ behavior, including:</p><p>1. Delete items<br>2. Edit quantity<br>3. View item detail</p><p>There are many shopping apps in the market and various shopping cart design. But basically the debate is alway between aesthetics and functionality(easy to use). We can put those designs into 2 categories. I will use Zara and Wish as the example of each category to analyze the difference of design intention.</p><h3>Zara: Aesthetics first functionality second.</h3><p>Zara’s App uses ‘edit‘ button to view/hide ‘edit quantity’ and ‘delete item’ to keep a clean layout. However, the disadvantage is that users have to take extra clicks to edit quantity or delete items.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/906/1*nFkXKZ8LVaopmbLpPu_5iA.png" /><figcaption>Diagram of Zara app’s shopping cart</figcaption></figure><h3>Wish: Functionality first aesthetics second.</h3><p>On the contrary, Wish’s App simply puts everything on the page. Users can modify almost anything with just one click. Please note the word — ‘Almost‘: for the ‘edit quantity‘ button, although it looks like it is a one-click action, it actually takes 3 clicks to finish the task. And of course, too many buttons make the layout less sophisticated.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/906/1*weWv5MwbXh-NPtIpAo_wxQ.png" /><figcaption>Diagram of Wish app’s shopping cart</figcaption></figure><h3>Functionality or aesthetics? Data drives design.</h3><p>Personally, I am a big believer of ‘Form follows function.’ But a good design should not give up aesthetics because of functionality. Sounds like a dilemma? It is the challenge to the designers. Back to the topic, the problem I was facing is how to balance those 2 factors and deliver a product that meets our users’ need. To answer this question, I calculated the numbers of users who delete items, view item detail and edit quantity in the shopping cart page:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/906/1*EPntOIe6-EorCcHpP4wLNA.png" /></figure><p>From the data above, we can easily see the weight of each action and the conclusion of the design: ‘delete items‘ and ‘view item detail‘ are commonly-used actions and users should use less clicks to accomplish the task; ‘Edit quantity‘ button is rarely used and it is ok to take extra steps. Looks like Wish is the winner? Yes and no. Yes, because it is easier to use functionality wise, and no, because its design can still be improved.</p><h3>Bieyang: Data + innovation</h3><p>Based on the data and aesthetic requirement, I want the page to be both easy to use and cleanlooking. Here is my solution: I keep the ‘delete’ button on the page, so users can delete any item with one click. However, I removed the ‘edit quantity‘ button to keep the layout less noisy. Users can edit the quantity in the detail page after they click the item.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/906/1*8v-DWsxzb7dEVlez46JYXg.png" /><figcaption>Diagram of Bieyang app’s shopping cart</figcaption></figure><p>If you wanna see more my works, please visit my website at <a href="http://www.chengfolio.com/work">www.chengfolio.com</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6c739fcab6ef" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>