<?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 Yubing Zhang on Medium]]></title>
        <description><![CDATA[Stories by Yubing Zhang on Medium]]></description>
        <link>https://medium.com/@yubingz?source=rss-82ce58d71ae8------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*mk2vpQnxrIZc73YI2aPanw.jpeg</url>
            <title>Stories by Yubing Zhang on Medium</title>
            <link>https://medium.com/@yubingz?source=rss-82ce58d71ae8------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Mon, 16 Nov 2026 15:09:33 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@yubingz/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[How to create a design system for white label apps]]></title>
            <link>https://uxplanet.org/how-to-create-a-design-system-for-white-label-apps-5350551ccf78?source=rss-82ce58d71ae8------2</link>
            <guid isPermaLink="false">https://medium.com/p/5350551ccf78</guid>
            <category><![CDATA[design-systems]]></category>
            <category><![CDATA[inclusive-design]]></category>
            <category><![CDATA[white-label]]></category>
            <category><![CDATA[accessible-design]]></category>
            <category><![CDATA[flexibility]]></category>
            <dc:creator><![CDATA[Yubing Zhang]]></dc:creator>
            <pubDate>Wed, 19 Feb 2020 23:48:37 GMT</pubDate>
            <atom:updated>2020-02-20T18:55:44.957Z</atom:updated>
            <content:encoded><![CDATA[<p>For the past two years, I have been working on a design system for Brightloom’s white label app business. Unlike most of design systems, it also needs to be highly rebrandable, scaleable, and accessible.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gxq7TLuNY85n704AuE3mwg.png" /></figure><h3>Challenges</h3><p>A design system is a collection of reusable components, guided by clear standards, that can be assembled together to build a variety of applications. As a design system for restaurant white-label apps, it needs to be highly rebrandable, accessible, and flexible.</p><h4>Rebrandable</h4><p>Restaurants should be able to bring their own branding to the system instead of compromising to fit within the system.</p><h4>Accessible</h4><p>To support consumer-facing apps, the design system is compliant with WCAG AA standards before and after rollouts.</p><h4>Flexible</h4><p>The design system can support different restuarants’ menu structures and customization models through configuration rather than re-engineering.</p><h3>Framework</h3><p>Instead of jumping into identifying every component in our current apps, I decided to take a step back to think about the entire framework and figure out a way to build a robust and scalable system.</p><p>Following the atomic design methodology, I decided to break the system down into three levels: Elements, Components, and Patterns.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*j4TXXCQDBZTNGkbXGqXLkQ.png" /></figure><p>Separating the system into 3 layers helped me isolate each restaurants’ unique branding from other concerns. This way, I won’t have to start from scratch every time a new restaurant buys our apps, nor will I produce individual components that are too rigid and compromise restaurants’ branding.</p><h3>Elements</h3><p>Elements lay the foundation for the entire design system. This layer includes colors, typefaces, grids, and spacing.</p><p>Using a title as an example, its color, font size, font weight, line height and spacing come from the elements system. This way, I can prevent inconsistencies in final designs.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6JpQQqalYSxpYm6Y8D5GvQ.png" /></figure><h4>Color system, not palette</h4><p>Colors not only define the look and feel of the entire interface but also communicate visual affordance to users. I wanted to create a color system that allows every restaurant to apply their own color palette instead of just one or two colors.</p><p>To achieve that, I decided to created two-level color system: primary color palette and neutral color palette. The primary color palette is made of colors with clear and actionable meanings.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*T48k-ETMtk0IINPEH_5rwA.png" /></figure><p>Because I’m designing white-label apps, I shouldn’t and can’t assign specific colors to the primary color palette. Restaurants’ branding colors will be applied to the primary color palette during rollouts.</p><p>However, most restaurants’ branding style guides have colors that express the branding in marketing materials but aren’t intended to be used for UI elements. I set up a color contrast test to make sure the rebranded app will be WCAG AA compliant.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*J76jBbCbgKMKbj1cVCS4ww.png" /></figure><p>If branding colors don’t meet the requirement, I will tweak the hue, saturation, and brightness to come up with a new color which has a better contrast ratio but is still in the same family as the old one.</p><p>As opposed to the primary color palette, secondary colors are not associated with a specific purpose. Secondary colors are largely used as background color for pages, cards or sections. To support the increasing demand for both light and dark mode apps, I created two default secondary color palettes: “light” and “dark”.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0ybTNdP1ndYv-9Jf2qq6nQ.png" /></figure><p>Every color in the white theme has its corresponding paired color in the dark theme. For example, Light 100 is the background color for light theme. When switching from to the dark theme, simply replace Light 100 with Dark 100.</p><h3>Components</h3><p>Components are made of elements and perform a well-defined function in the application.</p><p>In my definition, a component can be a button, page title, etc. For example, when a primary CTA button shows up on the screen, it guides users to the desired action.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KrXLyZ6clYFzdFJlOKjZLw.png" /></figure><h4>Using buttons as an example</h4><p>Buttons allow users to make choices and take actions with a single tap. Depending on the use case, there could be multiple actionable targets in one screen, like a list of salad bowls. There could also be multiple actions users can take per actionable target, like customize a salad or add it as-is to the cart.</p><p>Instead of using one button system throughout the entire app, I wanted to create a two-tier button system to serve varying use cases.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HBYi3HmcIrmbynwGekZEmg.png" /></figure><p>When there is only one preferred actionable target on the page, use the primary button system. If there are multiple actionable targets, using primary buttons can be confusing and overwhelming.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zmo9gK76qGshBEe0e8smGQ.png" /></figure><p>Secondary buttons are used when there is more than one actionable target on the screen, such as an item list view showing 2+ items and the interface cannot predict which item is the most common choice.</p><p>Unlike other components, buttons have more rebranding concerns. For example, some restaurants want rounded corners and some prefer the modern feeling of sharp corners. I made sure our system could be configured to support the most common needs.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FlVdWEZ2qZuusrdRtrYC8A.png" /></figure><h3>Patterns</h3><p>Patterns are well-assembled components to support certain features, which promotes logic and consistency across all the products.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Wkae4MRBv66TGipN2vDfww.png" /></figure><p>Patterns or modules are an especially userful concept for a white-label app. When facing different restaurant menus and customization models, instead of redesigning the entire item detail interface from scratch, we can just change some configuration and keep the rest of the app the same.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nlDm0P-jnuRvQe16_Pxt-A.png" /></figure><p>In this way, the design system can not only support a more agile product development process for designers but also support more rapid restaurant onboarding for engineers.</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&amp;key=d04bfffea46d4aeda930ec88cc64b87c&amp;type=text%2Fhtml&amp;schema=upscri" width="800" height="400" frameborder="0" scrolling="no"><a href="https://medium.com/media/a7ecd953714a6022a3456ca263d5f43b/href">https://medium.com/media/a7ecd953714a6022a3456ca263d5f43b/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5350551ccf78" width="1" height="1" alt=""><hr><p><a href="https://uxplanet.org/how-to-create-a-design-system-for-white-label-apps-5350551ccf78">How to create a design system for white label apps</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>
        <item>
            <title><![CDATA[Designing for large touch screen — Always have the user context in mind]]></title>
            <link>https://uxdesign.cc/designing-for-large-touch-screen-always-have-the-user-context-in-mind-878b6d2e02a9?source=rss-82ce58d71ae8------2</link>
            <guid isPermaLink="false">https://medium.com/p/878b6d2e02a9</guid>
            <category><![CDATA[interaction-design]]></category>
            <category><![CDATA[user-research]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[touchscreen]]></category>
            <dc:creator><![CDATA[Yubing Zhang]]></dc:creator>
            <pubDate>Sun, 15 Oct 2017 17:12:57 GMT</pubDate>
            <atom:updated>2018-12-03T05:59:25.272Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vhuVNQvNpAfSd7xeSbJQEg.png" /></figure><p>Most of designers have experiences in designing for desktop or mobile interface. So do I. But three months ago, I was challenged to design for a large touch screen of food vending machine. The screen is 22 inches. What does this mean?</p><p>The screen size is about 14 times larger than that of the average smart phone, and 8 times larger than that of iPad mini and 3 times larger than that of iPad. The significant difference in size has a real impact on user behavior.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/169/1*hC0P8oHU9h6YDtQjTldi_A.png" /></figure><h4><strong>Hand movement</strong></h4><p>It’s easy to realize that facing a larger screen size significantly increases the interaction efforts of tapping, typing, and moving between screens. They are more likely to access the interface at extended arm’s length and must hold their hands in the air, which increases fatigue.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/169/1*ylkxO0ecpdHmtrfjnNkXKw.png" /></figure><h4><strong>Eyes scanning</strong></h4><p>Using smartphones, users can take in the whole screen at one glance. With a large screen, they must move their heads around to see all parts of the interface, which requires more effort from users.</p><p>Clearly, my story about large touch screen interface design went beyond that. Mentally, users also have different feelings about large touch screen. I first did an image board to understand where do people usually get access to large touch screen — the user context.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QaWohV_JUlPa8cPuCxZydg.png" /></figure><p>This image board helps me imagine <strong>a user standing in front of a large machine in a public space, using her index finger to touch the screen and trying to focus on its image without becoming distracted by the people around her. What she would be concerning at that moment?</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/169/1*8RkkUFcSMp67ec0taj5UJw.png" /></figure><h4><strong>The sense of familiarity</strong></h4><p>The most common used large touch screen design for everyone might be ATM and gas pumps, ticket kiosks or museums. But people are reluctant to touch large displays when they are not sure whether they will derive any benefit from the effort.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/169/1*SDy4EyFfvzu7Bx-NTFxtmg.png" /></figure><h4><strong>The matter of privacy</strong></h4><p>With larger touch screens, there is usually enough space for two or three people to interact at the same time. The negative side to screen sharing is that they offer little or no privacy for users of large, public touchscreen. With big touchscreen design, requiring users to provide sensitive information is problematic.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*EUU6htbErTAwiPs8x5mJ-w.png" /></figure><h4><strong>The interaction between human and machine</strong></h4><p>People make the effort to input their information for something as a return so unlike an app or website, there is a realtime communicate happening between users and the machine. The interface must work as a bridge between users and the machine.</p><p>All of these issues encouraged me to think critically about how to design in a user context.</p><h3>A tough lesson I learned</h3><p>With so many concerns and the pressure of moving fast in my mind, I first created a medium-fidelity interface with a layout and flow design for user testing. Since most users are unfamiliar with the big touchscreen interface, I drew my inspiration from Web design, using a header menu for the shelves and a footer menu to illustrate all the other functions.</p><ul><li>I expect users to draw lessons from their experience using websites when trying our interface.</li><li>It would be easier for users to use the screen when all content stays in the middle of the screen.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*639_b4hy4mKwj-h03EP1QA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wPmWQfJKie3YUwYjSMbWaw.png" /></figure><p>I created a demo in Invision and received 90 percent position feedback from user testing. All respondents were able to complete a purchase easily and understand how the machines functioned. At that point, however, I encountered my greatest challenge with this project. In the actual machine interface, the buttons and menus did not respond readily to touch, which makes for a high error rate.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KkPi9drx_ZL2l1R9DqN4_A.png" /></figure><p>Consequently, I had to rethink my previous work.</p><h3>Unlike other designs, large touch screen design is closely integrated with its specific context.</h3><p>Clearly, since the screen is positioned at an angle in relation to the machine, when users view the machine, they always perceive both a hit target area and an off-screen hit area. <strong>Having all touchable items appear flat, as in my former design, makes the perceived hit target and on-screen area too limited for most users in a distracting environment.</strong></p><p>The design for large touch screen is very different from that of my previous project; in this case, the user is expected to stand in front of the machine in a public space where people are talking or walking around. This special user context is actually the key to the project. I learned a lesson from the initial medium fidelity flat clickable design, and also acknowledged the gap between digital demo user testing and real situation testing. This project, therefore, has strongly changed my understanding about design and testing in a real-world context.</p><p>The final design is still under progress. Also, I didn’t talk much about privacy and human-machine communication design, if you are interested, you are welcome to read the whole project on <a href="http://yubing.me/">my portfolio</a> or <a href="http://yubing.me/resume/">contact me</a> if you want to talk. Thanks for your time!</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fupscri.be%2Ff%2F50d69a%3Fas_embed%3Dtrue&amp;dntp=1&amp;display_name=Upscribe&amp;url=https%3A%2F%2Fupscri.be%2F50d69a%2F&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=upscri" width="800" height="400" frameborder="0" scrolling="no"><a href="https://medium.com/media/05d5fd32eda31cbd1b83287606744532/href">https://medium.com/media/05d5fd32eda31cbd1b83287606744532/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=878b6d2e02a9" width="1" height="1" alt=""><hr><p><a href="https://uxdesign.cc/designing-for-large-touch-screen-always-have-the-user-context-in-mind-878b6d2e02a9">Designing for large touch screen — Always have the user context in mind</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>
    </channel>
</rss>