<?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 Brian Smith on Medium]]></title>
        <description><![CDATA[Stories by Brian Smith on Medium]]></description>
        <link>https://medium.com/@brianisrighthere?source=rss-1645b992d23a------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*nVMNeDyval_TGFQo.jpg</url>
            <title>Stories by Brian Smith on Medium</title>
            <link>https://medium.com/@brianisrighthere?source=rss-1645b992d23a------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Mon, 16 Nov 2026 02:13:52 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@brianisrighthere/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 Crucial Role of Product Design in the AI Revolution]]></title>
            <link>https://medium.com/@brianisrighthere/the-crucial-role-of-product-design-in-the-ai-revolution-4f3f7ec19d83?source=rss-1645b992d23a------2</link>
            <guid isPermaLink="false">https://medium.com/p/4f3f7ec19d83</guid>
            <category><![CDATA[artifical-intellegence]]></category>
            <category><![CDATA[product-design]]></category>
            <dc:creator><![CDATA[Brian Smith]]></dc:creator>
            <pubDate>Fri, 10 May 2024 15:24:32 GMT</pubDate>
            <atom:updated>2024-05-10T15:24:32.485Z</atom:updated>
            <content:encoded><![CDATA[<p>As businesses embark on the transformative journey into artificial intelligence, the role of product design becomes more pivotal than ever. In an era where AI is set to redefine industry standards, thoughtful product design is essential for creating intuitive, user-centric solutions that harness the power of AI effectively.</p><p>Integrating AI into product design isn’t just about leveraging technology to enhance functionality — it’s about reimagining how products interact with users. Designers must consider AI not only as a tool but as a core component that influences every aspect of the user experience. From predictive user interfaces that anticipate needs to adaptive features that evolve with user interactions, the possibilities are vast.</p><p>The new role of product designers will be focused on creating a wholistic experience where apps become a magical experience.</p><p>Moreover, AI can enable designers to achieve new levels of personalization, making products feel more responsive and tailored to individual users. This shift requires a deep understanding of both technology and human behavior, pushing designers to adopt a multidisciplinary approach.</p><p>For companies willing to pioneer these advancements, the reward is a competitive edge in a market that increasingly values smart, seamless, and personalized user experiences. Embracing AI in product design is not merely an enhancement — it’s becoming a necessity for staying relevant in a fast-evolving marketplace.</p><p>When considering whether your business should <a href="https://www.fullstack.com/labs/resources/blog/your-company-will-be-an-ai-company-a-look-inside-the-next-business-revolution">integrate artificial intelligence</a> into your processes, it’s necessary to consider what will happen to your business if you don’t.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4f3f7ec19d83" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Remote Usability Testing]]></title>
            <link>https://medium.com/@brianisrighthere/remote-usability-testing-d6735f9b6be0?source=rss-1645b992d23a------2</link>
            <guid isPermaLink="false">https://medium.com/p/d6735f9b6be0</guid>
            <category><![CDATA[remote-usability-testing]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[usability-testing]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[user-research]]></category>
            <dc:creator><![CDATA[Brian Smith]]></dc:creator>
            <pubDate>Fri, 15 May 2020 22:29:27 GMT</pubDate>
            <atom:updated>2020-05-15T22:35:43.335Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5ZhIX3ccVozWA9ltIQslYw.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@freestocks?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">freestocks</a> on <a href="https://unsplash.com/s/photos/app?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>When designing a new product or iterating on features of an existing product, you have to start by designing based on your own assumptions. Once you have a prototype, you can use that to validate whether your assumptions and personal biases were valid for the users of the product. That process of validation is called usability testing. Usability testing is a form of qualitative research that can be done effectively in person, but this requires a lot of coordination of calendars and is often impossible due to geographic location. Luckily, with tools such as Zoom and Google Meet, usability testing can be done remotely. This guide will help you make the most of your remote usability testing and will cover:</p><ol><li>Defining Goals &amp; Target Group</li><li>Identifying Testers</li><li>Writing Assumptions</li><li>Writing the Test Script</li><li>Conducting the Test</li><li>Compiling &amp; Analyzing the Results</li><li>Writing Up Your Findings</li></ol><h3>Defining Goals &amp; Target Group</h3><p>Every usability test should have a goal in mind. Document what that goal is. You might be looking to decrease the time it takes to sign up, or improve customer satisfaction. Knowing that goal as you go into the testing process will help craft the entire test. What types of users could the feature you’re testing impact? It’s important to know who the audience is so that you don’t have someone completely unfamiliar with the industry you are designing for.</p><h3>Identifying Testers</h3><h4>Who Should You Pick?</h4><p>Find people who fit the profile of the user group that will be affected by the feature. Make sure they will be able to technically participate in the test. With remote testing, it’s ideal that they have access to a reliable internet connection, a webcam, and are reasonably proficient with the basics of computers.</p><h4>How Many Testers is Ideal?</h4><p>Four to six testers should give enough variance in the feedback. Additional testers may be required for more complex sessions, but fewer than four may give you skewed results based on just one unhappy tester. Nielsen Norman suggests that using <a href="https://www.nngroup.com/articles/why-you-only-need-to-test-with-5-users/">five testers</a> results in the most efficient testing process.</p><h3>Writing Assumptions</h3><p>When designing a solution without testing it on users, you are doing so based on the assumptions you have made through your research process. You’re trying to understand who the users are and the goals they hope to achieve with your app. Those assumptions serve as your baseline in the usability test. For example, “We assume that users will prefer logging in by connecting their Google account”. By identifying this as your assumption, you now have something to test against; will users choose Google login over other options?</p><h3>Writing the Test Script</h3><p>Using a three-phased approach to structure the test session will help ensure that the test does not get derailed. The three phases can be described as context gathering, scenario setting &amp; tasks, and debrief.</p><h4>Context Gathering</h4><p>To begin the session it’s useful to spend some time breaking the ice with the tester. It will help them feel more at ease and will help you understand the context they come into the test with. Some possible questions might be;</p><ol><li>How are you doing today?</li><li>Tell me a bit about yourself…</li><li>What do you do for work?</li><li>Have you done this sort of testing before?</li><li>How comfortable are you with technology?</li></ol><h4>Scenario Setting &amp; Tasks</h4><p>The best results from testing will come from the tester understanding a bit about the app and how or why they might be arriving at the task you are about to ask them to complete. This scenario is the hypothetical situation they would be in for the task. For example:</p><blockquote><strong>Scenario: </strong>You are in a new city and are trying to meet with a client to close an important deal. A coffee shop would be too casual for this type of meeting. You only have 2 hours until the meeting is supposed to begin.</blockquote><blockquote><strong>Task: </strong>Get out your phone, open the app, book a conference room, and send an invite to your client to join you.</blockquote><h4>Debrief</h4><p>After completing the tasks, you should gather feedback from the tester on the experience. This is the most critical part of the test script. Lacking or poorly written questions will confuse users or not elicit the detailed results you were hoping for.</p><h3>Conducting the Test</h3><p>Before testing with your target audience, run a pilot test with a colleague to ensure there are no misleading questions or anything you may have left out. Preparing the tester for the process is also a good idea. Send an email to the tester a few days in advance that introduces yourself, describes the process, the time commitment, and briefly describe what you hope to accomplish.</p><p>With remote sessions, it’s important for the tester to be comfortable and not like a lab rat. If they feel that <em>they </em>are being tested rather than <em>the system</em>, the tester will be tempted to do what you expect them to do rather than what they would naturally do. To help with this, never conduct remote testing with more than yourself and the tester on the call.</p><p>When the call begins, start with an introduction of who you are and thank the tester for their time. Then start with your script by asking the Context Gathering questions. Keep the tone informal and enjoyable to help develop trust with the tester.</p><p>Before jumping into the Scenarios and Tasks, orient the tester with a few suggestions;</p><ol><li>Encourage the tester to talk through their process and emotions as they are completing tasks.</li><li>Remind the tester that there is no wrong way to complete the tasks.</li><li>Let them know that you won’t be offended by any of their feedback, and that they should be as honest and blunt as possible.</li></ol><p>Then get started with the first scenario and task. If the tester gets stuck at any point and isn’t sure what to do, try not to lead them. Instead ask, “what do you think you should do next?” or “how do you think you could go back a step to try again?”.</p><p>During the test, don’t write detailed notes on their process, record the session so that you can go back and do that later. You want to be paying attention to what they are doing and quickly noting the results. A simple method of noting results during the session is to score their completion of the task on a 0–10 scale, and the amount of time it took. If they successfully complete the task, that’s a 10. If they couldn’t complete it at all that’s a 0. For partially completing the task, mark a number that represents how far they were able to get in the task. Noting the amount of time taken to complete the task will help you understand how easy the task was for the tester to complete.</p><p>After completing the tasks, it’s time to debrief. Ask follow up questions about how they felt during the tasks, what they wish they could have done but couldn’t, what (if anything) was particularly enjoyable about the process, or what (if anything) was particularly frustrating about the process.</p><h3>Compile &amp; Analyze the Results</h3><p>For each test, you’ll have a scorecard and a video recording of the session. Go back through the video and write down any salient points, then categorize those notes into topics. At this point, you should begin to notice themes developing in the results. Consider the “why” behind the results. For example, you notice that 60% of the testers got stuck at the checkout page. This is the time to consider why this is happening; what in the UX could be causing this issue?</p><h3>Write Up Your Findings</h3><p>In order to turn the findings into actionable items, you should write a summary of the findings. Include details on your hypothesis going into the test, how it was conducted, data points from the results, and the conclusions you draw from them. These findings will help those who were not involved in the process understand the actions that should be taken as a result of the testing.</p><h3>Conclusion</h3><p>This isn’t a one-and-done process. After your first test, make some revisions to the UX and conduct another test. This way, you’ll be able to validate that the changes you made were warranted. Usability testing helps remove the unknowns and assumptions from your design process which results in greater efficiency in your product development process. Ultimately, you should save the client time and money, and give them a higher quality product that their users will actually enjoy using.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d6735f9b6be0" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Designing and Building Apps With Material Design]]></title>
            <link>https://medium.com/@brianisrighthere/designing-and-building-apps-with-material-design-d3fb0d896cca?source=rss-1645b992d23a------2</link>
            <guid isPermaLink="false">https://medium.com/p/d3fb0d896cca</guid>
            <category><![CDATA[material-design]]></category>
            <dc:creator><![CDATA[Brian Smith]]></dc:creator>
            <pubDate>Sat, 28 Sep 2019 22:50:52 GMT</pubDate>
            <atom:updated>2019-09-28T22:50:52.755Z</atom:updated>
            <content:encoded><![CDATA[<p>At <a href="https://www.fullstacklabs.co/">FullStack Labs</a>, we use <a href="https://material.io/">Google’s Material Design</a> spec to design and build most of the apps we work on. Material Design is a framework of design patterns and components that that unite style, branding, interaction, and motion with a common set of principles.</p><p>Google began developing the spec in 2014 using more man(or woman)power than any other company in the world possibly could, and based the spec on more real-life experience than you could imagine. With that in mind, Material has become one of the most well document and tested design specifications ever. We all know that what is new today will be old and dusty 5 years from now. Luckily, Google continually updates and enhances the spec to reflect modern user behaviors. (<a href="https://www.invisionapp.com/blog/material-design-google-2018/">View Details of the 2018 MD updates</a>)</p><p>When designing apps, we are able to create high-fidelity prototypes quickly by using a library of design components that comply with the Material Design specifications. Our development team uses code libraries that are built with the same principles that the design team is prototyping with. <strong>This unification of design patterns and web components allows for a highly efficient workflow. </strong>We regularly implement the <a href="https://material-ui.com/">“Material-UI”</a> library because of its compatibility with <a href="https://www.fullstacklabs.co/react-developers">React</a> and <a href="https://www.fullstacklabs.co/react-native-developers">React Native</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1w5aE_7yMisxHrRicdBTdw.png" /><figcaption>A sampling of Material Design components we use.</figcaption></figure><p>The principles of <a href="https://material.io/">Material Design</a> include iconography, typography, responsive layouts, onboarding, and how to introduce users to new features. Each principle is thoroughly documented with do’s and don’ts for a solid user experience.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KNnFvCKswayExsI4FEfQ9Q.png" /><figcaption>Examples from the Material Design documentation.</figcaption></figure><p><strong>But what if Material Design doesn’t support a feature you need?</strong> Well, we’ve found that rarely to be the case. The Material Design documentation is extensive already and continues to expand each year it is around. In the case that you truly need something that the spec doesn’t mention, we design a custom component using the overarching principles of Material Design.</p><p><strong>But won’t my app just look like Google?</strong> If used properly, your app will look top notch, highly functional, and represent your brand well. Don’t believe us? Have a look for yourself at some of the designs we’ve created using Material Design.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cFhL0vnkzSkZdiQrZdPPiw.png" /><figcaption>An office space rental platform for SpaceMX.com</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ucqugJ5UNI578BxbYJWXfw.png" /><figcaption>A dashboard for managing Ekso’s robotic exoskeleton use.</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VeFTX5d-s3L22eov28MaWA.png" /><figcaption>A marketing collateral design editor for LRESocial.com</figcaption></figure><p><strong>Interested in building an app with Material Design?</strong> <a href="http://fullstacklabs.co/">Drop us a line</a>. We’d love to hear about your next project.</p><p>Link Dump:</p><ul><li><a href="http://material.io/">Material Design</a></li><li><a href="http://material-ui.com/">Material-UI</a></li><li><a href="http://fullstacklabs.co/">FullStack Labs</a></li><li><a href="http://www.plasterdesignsystem.com/">Plaster Sketch Components</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d3fb0d896cca" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Material Studies: Floating Action Button]]></title>
            <link>https://medium.com/@brianisrighthere/material-studies-floating-action-button-22715e2f1145?source=rss-1645b992d23a------2</link>
            <guid isPermaLink="false">https://medium.com/p/22715e2f1145</guid>
            <dc:creator><![CDATA[Brian Smith]]></dc:creator>
            <pubDate>Fri, 30 Nov 2018 16:47:24 GMT</pubDate>
            <atom:updated>2018-11-30T16:50:48.859Z</atom:updated>
            <content:encoded><![CDATA[<blockquote><em>This document references content directly from the Material Design Documentation. To learn more, go to: <br></em><a href="https://material.io/design/components/buttons-floating-action-button.html#">https://material.io/design/components/buttons-floating-action-button.html#</a></blockquote><blockquote><em>Intended for training purposes at FullStack Labs only.</em></blockquote><h3>Usage</h3><p>Represents the primary or most common action on a screen. It comes in three types: regular, mini, and extended.</p><p>Only use a FAB if it is the most suitable way to present a screen’s primary action.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7feMqgMn0nlSJGUokNjVpA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*30FkGG5yUp4SsiMZRGuGyw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*muZVlHy8pkHx_F9WFe1p-w.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UCzqEAdZJPwzXzAv0n1PPg.png" /></figure><h3>Placement</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qYaBvzctScnaIhBsFatGGg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hZEnqZml30NUQ8Bn7BgiCg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/778/1*U55A3XICPrgRl24RI4B-uA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/768/1*9EKemNiI6B-qL_7LDc4iGQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/776/1*HaZf7Ha5u06LOPCZ4pkZ5A.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RvlGblEYYY877ypO8Zyhaw.png" /></figure><h3>Principles</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Q2gxq-5CxZFE9tNtH2vCxQ.png" /></figure><h4>A floating action button (FAB) can trigger an action either on the current screen, or it can perform an action that creates a new screen.</h4><p>A FAB promotes an important, constructive action such as:</p><ul><li>Create</li><li>Favorite</li><li>Share</li><li>Start a process</li></ul><p>Avoid using a FAB for minor or destructive actions, such as:</p><ul><li>Archive or trash</li><li>Alerts or errors</li><li>Limited tasks like cutting text</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Fg-VOJlHwtduGe51fd7q3w.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gXptPkRYz8KNoyXndwLc8Q.png" /></figure><h4>Speed dial</h4><p>When pressed, a FAB can display three to six related actions in the form of a <strong>speed dial</strong>. This transition can occur in one of the following ways:</p><ul><li>Upon press, the FAB can emit related actions</li><li>Upon press, the FAB can transform into a menu containing related actions (Android only)</li></ul><p>If more than six actions are needed, something other than a FAB should be used to present them.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/680/1*jYWcmjzStiRpB7gDfGTa2w.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*NG_RYF7Mhro-Ho9c1bQJtA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Ds1F3tYDVN4mX4IwraynnQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ll8WFVT7mvLmCOWGGaLB3g.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6q-ti0w16tJZerq2NrGyZA.png" /><figcaption>Upon press on Android, the FAB can transform into a menu containing related actions. A scrim indicates that functionality outside of the action menu is temporarily disabled. The menu remains on-screen until an action, or the scrim, is tapped.</figcaption></figure><h4>Tabbed Screens</h4><p>When tabs are present, the FAB should briefly disappear, then reappear when the new content moves into place. This expresses that the FAB is not connected to any particular tab.</p><p><a href="https://storage.googleapis.com/spec-host-backup/mio-design%2Fassets%2F1CFlxacAgTNwbHddEylfR0iqC6LBtLbej%2Ffab-layout-transition-do-v01.mp4">The function of the FAB can change per tab</a>.</p><p><a href="https://storage.googleapis.com/spec-host-backup/mio-design%2Fassets%2F1B5uWW91oEZtlqp2bKP9uzNT_41MgGPkz%2Ffab-layout-transition-dont-v01.mp4">The FAB does not move in unison with the tabbed screen.</a></p><h3>Transitions</h3><p><a href="https://storage.googleapis.com/spec-host-backup/mio-design%2Fassets%2F1DKiMU5LEKus0Beh3Vmmad3eQTgN8hohD%2Ffab-morph-v1.mp4">The FAB can transform into another surface in an app. Morphing should be reversible and transform the new surface back into the FAB.</a></p><p><a href="https://storage.googleapis.com/spec-host-backup/mio-design%2Fassets%2F1Lilaq13K-G32kkTgZgS5iJ5lnAYHwexE%2Ffab-toolbar-fullscreen-v06.mp4">The FAB can transform into a new surface that spans the entire screen. This type of transformation is typically for creating new content.</a></p><h3>Types of FABs</h3><ol><li>Default (56 x 56dp)</li><li>Mini (40 x 40dp)</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8uZfg_bb4yXZRofnKnVzBw.png" /></figure><p>3. Extended</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*F2b6uhMBVuj7r2ze3jA-sg.png" /><figcaption>The extended FAB is wider, and it includes a text label</figcaption></figure><p>The width of a extended FAB’s container can be fixed or fluid.</p><ul><li>A fixed width container is defined by the cumulative width of the icon, text label, and padding.</li><li>A fluid width container is defined by its relationship to something else on screen, such as screen width or the layout grid.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3jElnWgosLMCLCiLVyue0A.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6lV8TGEXfArWQdSLyKS2cg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/770/1*IRMdUzwTiTuFWzxVX2cNdA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/760/1*3XN_rJlW7mg2UViAVEd9_Q.png" /></figure><h4>An extended FAB can transform into a standard FAB when a screen is scrolled.</h4><ul><li>The FAB should not return to an extended FAB until the user scrolls back to the top of the page.</li><li><a href="https://storage.googleapis.com/spec-host-backup/mio-design%2Fassets%2F1OTb9HPdZYx_7NVc3cizpA0T4ItMRb9Xi%2Fefab-scroll.mp4">Extended FAB transforming into a standard FAB after the user scrolls to the top of the page</a></li></ul><h3>Specs</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FIkI_s3nAp9AIWnVJMEDqg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WkXdpIzPlkTrux8Dy72jTg.png" /></figure><h3>Components</h3><p><a href="https://material-ui.com/demos/buttons/#floating-action-buttons">Material-UI</a></p><p><a href="https://callstack.github.io/react-native-paper/fab.html">Paper</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=22715e2f1145" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Material Studies: Tables]]></title>
            <link>https://medium.com/@brianisrighthere/material-studies-tables-4e0111fe71a1?source=rss-1645b992d23a------2</link>
            <guid isPermaLink="false">https://medium.com/p/4e0111fe71a1</guid>
            <dc:creator><![CDATA[Brian Smith]]></dc:creator>
            <pubDate>Thu, 15 Nov 2018 22:53:03 GMT</pubDate>
            <atom:updated>2018-11-15T22:53:03.394Z</atom:updated>
            <content:encoded><![CDATA[<blockquote><em>This document references content directly from the Material Design Documentation. To learn more, go to: <br></em><a href="https://material.io/design/components/data-tables.html#">https://material.io/design/components/data-tables.html#</a></blockquote><blockquote><em>Intended for training purposes at FullStack Labs only.</em></blockquote><h3>Usage</h3><p>Data tables display information in a way that’s easy to scan, so that users can look for patterns and insights. They can be embedded in primary content, such as cards.</p><p>When including tools, they should be placed directly above or below the table.</p><h3>Anatomy</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*5ygjB2HJ0iicapUP.png" /></figure><ol><li>Container<br>The container holds all data table content.</li><li>Column header<br>Column headers are titles for column content.</li><li>Sorting tool<br>Sorting tools allow users to reorder table content, appearing only on hover.</li><li>Row checkbox<br>Checkboxes allow users to select a row.</li><li>Table content<br>Tables contain raw data.Components</li></ol><h4>Column Header</h4><p>By default, there is 56dp of padding between columns. Column headers that extend into this padding can either:</p><ol><li>Enable horizontal scrolling, so users can scroll to see the full column name</li><li>Shorten the column name, while displaying it in full in a tooltip (on hover)</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/720/0*gt93UUnSN8THIzf5.png" /></figure><h4>Sorting</h4><ul><li>Left-most column is sorted by default, with an indicator displayed in the column header.</li><li>Tapping the header of the sorting column reverses the sort order, also rotating the sort icon 180 degrees.</li></ul><h4>Row Checkbox</h4><ul><li>When a checkbox for a row is selected, the row should display a background color.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*g3n_oYfp7apgoZXWNbrunw.png" /></figure><h4>Row Hover</h4><ul><li>Display a background color in that row.</li><li>If individual table cells have specific hover states, display both that cell’s hover state as well as the row hover state.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XubzAHyadMcZg92pN4ZQOg.png" /></figure><h4>Column Hover</h4><p>On hover, two things can be displayed:</p><ul><li>A tooltip displaying more information about each column header</li><li>A sort icon in the column header, if sorting is enabled</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YebJ7NnjNMnziauzdmzGmw.png" /></figure><h4>Inline Text Editing</h4><ul><li>Tables can include editable fields for text editing or adding comments.</li><li>They are indicated by placeholder text in the field.</li><li>On tap, an edit dialog with a text field or a full dialog is displayed.</li></ul><p><strong>Small Dialog</strong></p><ul><li>Text can be edited using a small edit dialog, allowing users to confirm text by pressing Enter.</li><li>Dialog edges should align with nearest divider line or table edge.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*y2WBtlOidYzSCwBGeHv_hg.png" /></figure><p><strong>Large edit dialog</strong></p><ul><li>A large edit dialog is a complex, flexible dialog box.</li><li>Users confirm text by tapping the Save button.</li><li>Dialog edges should align with the nearest divider line or table edge.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fd22YKtshZEmx7HVw05Tpw.png" /></figure><p><strong>Inline Edit Icon</strong></p><p>An inline edit icon allows field editing, with an icon at the opposite end of the cell from content.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ehGsDgWC8if3Hk7MQHSTbg.png" /></figure><h4>Inline Menus</h4><ul><li>Inline menus allow users to select from a predefined list of options.</li><li>These menus can be directly embedded in a table.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hvgGuym6x2bmTXotOnEwEA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7Upfmacmo9WWZlb1XQMUow.png" /></figure><h3>Tables Within Cards</h3><p>Tables can be embedded within a card. At the bottom of each card, tools can be displayed for table navigation and data manipulation.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Zs0FOao8h4xfm1zukJBvwg.png" /></figure><h4>Card Headers</h4><p>When tables in cards require actionable headers instead of titles, you can either:</p><ol><li>Display persistent actions</li><li>Display a contextual header that indicates when items are selected</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*I0A6diYz4mvgcxIFPm3kwg.png" /></figure><h3>Specs</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8mwKz7xIM4PDHfhnPloTMg.png" /></figure><h3>Components</h3><ul><li><a href="https://devexpress.github.io/devextreme-reactive/react/grid/docs/guides/fundamentals/">React Grid - Fundamentals - DevExtreme Reactive Components</a></li><li><a href="https://material-ui.com/demos/tables/">Table React component - Material-UI</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4e0111fe71a1" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Material Studies: Text Fields]]></title>
            <link>https://medium.com/@brianisrighthere/material-studies-text-fields-f029b3b38020?source=rss-1645b992d23a------2</link>
            <guid isPermaLink="false">https://medium.com/p/f029b3b38020</guid>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Brian Smith]]></dc:creator>
            <pubDate>Fri, 02 Nov 2018 14:51:21 GMT</pubDate>
            <atom:updated>2018-11-02T14:51:21.456Z</atom:updated>
            <content:encoded><![CDATA[<blockquote><em>This document references content directly from the Material Design Documentation. To learn more, go to: </em><a href="https://material.io/design/components/bottom-navigation.html#usage">https://material.io/design/components/bottom-navigation.html#usage</a></blockquote><blockquote><em>Intended for training purposes at FullStack Labs only.</em></blockquote><h3>Types</h3><ol><li>Filled Text Fields</li><li>Outlined Text Fields</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*jKpeKns2sXK7bfvO.png" /><figcaption>1. Filled Text Fields, 2. Outlined Text Fields</figcaption></figure><p>Note that both types visually appear interactive, making the fields discoverable in the UI. They look similar to buttons in form but contain obvious differences.</p><p>3. Text Fields No Fill (Deprecated)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_yQL2dO5ef9sNcI3nOgZOw.png" /></figure><p>The previous standard for text fields is no longer supported. This was a good move by Google. The text fields were easily missed in the UI because they did not appear interactive.</p><p>These fields are still available in Material-UI, but should not be used on new projects.</p><h3>Which Text Field Should You Use?</h3><p>Both types of text fields provide the same functionality, so the type of text field you use can depend on style alone.</p><p>Filled text fields carry more visual emphasis, making them stand out when surrounded by other content and components.</p><p>Outlined text fields have less visual emphasis than filled text fields, which helps simplify layout in places like forms, where many text fields are placed together.</p><p>Choose the type that:</p><ul><li>Works best with your app’s visual style</li><li>Best accommodates the goals of your UI</li><li>Is most distinct from other components (like buttons) and surrounding content</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/720/0*PT0q_CjRB7Md8zJY.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/720/0*cEkRyfDAOUA9XajO.png" /></figure><p>Both types of text fields provide a solid user experience, when discussing with clients one should not be presented as better than the other.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/720/0*tFk1BhPV2_Dppuiu.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/720/0*4DssQilqmH-rtHLE.png" /><figcaption>Left is acceptable, right is not.</figcaption></figure><p>It is possible to use both outlined and filled text fields in the same UI, but never in the same region. The types of fields should be used consistently.</p><h3>Anatomy</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*I4bgjCAdwucaZjOi.png" /></figure><ol><li>Container</li><li>Leading icon (optional)</li><li>Label text</li><li>Input text</li><li>Trailing icon (optional)</li><li>Activation indicator</li><li>Helper text (optional)</li></ol><h4>Container</h4><p>The container of a text field provides contrast from the background and surrounding content. It is important that the text fields are easily discoverable.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/410/1*7ihi5px3uL-AIOWaJZ0X5w.png" /></figure><p>Outline containers have a border around the entire field, while filled containers have a border only on the bottom.</p><p>Text field containers have rounded corners on all four corners for outline fields and only the top corners on filled text fields.</p><h4>Labels</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*UZ2uP_k5BG2s5j-c.png" /></figure><p>Labels should always be visible and move from the middle of the field to the top when active.</p><p>Text labels should never be truncated or wrap to multiple lines. Keep them short.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/904/1*wIpMJCdgIIaELCH3iA8KUA.png" /></figure><h4>Required Text Indicator</h4><p>To indicate that a field is required, display an asterisk (*) next to the label text and mention near the form that asterisks indicate required fields.</p><ul><li>If some fields are required, indicate all required ones</li><li>If most fields are required, indicate optional fields by displaying the word “optional” in parentheses next to the label text</li><li>If required text is colored, that color should also be used for the asterisk</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*vQq12Qa4vkNLKV-7.png" /></figure><h4>Input Text</h4><p>The text that the use has typed into the field, the cursor (2) indicates the current location in the text field.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/576/1*Hc6g_sKr9uni-8deEg7Q-g.png" /></figure><h4>Assistive Elements</h4><p>Assistive elements provide additional detail about text entered into text fields.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/720/0*qclQDHGScEPvD8Fr.png" /></figure><p>1. Helper text<br>Helper text conveys additional guidance about the input field, such as how it will be used. It should only take up a single line, being persistently visible or visible only on focus.</p><p>2. Error message<br>When text input isn’t accepted, an error message can display instructions on how to fix it. Error messages are displayed below the input line, replacing helper text until fixed.</p><p>3. Icons<br>Icons can be used to message alerts as well. Pair them with error messages to provide redundant alerts, which are useful when you need to design for colorblind users.</p><p>4. Character counter<br>Character or word counters should be used if there is a character or word limit. They display the ratio of characters used and the total character limit.</p><h4>Icons</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/714/1*m4O5J1Irm0P6fXgt50XNcw.png" /></figure><p>1. Icon signifier<br>Icon signifiers can describe the type of input a text field requires, and be touch targets for nested components. For example, a calendar icon may be tapped to reveal a date picker.</p><p>2. Valid or error icon<br>Iconography can indicate both valid and invalid inputs, making error states clear for colorblind users.</p><p>3. Clear icon<br>Clear icons let users clear an entire input field. They appear only when input text is present.</p><p>4. Voice input icon<br>A microphone icon signifies that users can input characters using voice.</p><p>5. Dropdown icon<br>A dropdown arrow indicates that a text field has a nested selection component.</p><h3>States</h3><h4>Filled Text Fields</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*OMOhYSk7sMDtN-i7.png" /></figure><h4>Outlined Text Fields</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Tkl4DSMETUnBJhhE.png" /></figure><h4>Input Types</h4><ul><li><strong>Single line text fields</strong> display only one line of text, as the cursor reaches the right side, the text automatically scrolls left</li><li><strong>Multi-line text fields</strong> grow to accommodate multiple lines of text and show all user input. The field dynamically expands with the user’s input</li><li><strong>Text areas</strong> are fixed-height fields. The large initial size indicates that longer responses are encouraged.</li></ul><h3>Specs</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/936/1*OLAtFR0KJKmqgFnh6xD9Sg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/928/1*XiYM_Jch0gPUB5E8GivKVQ.png" /></figure><h3>Components</h3><p>React: <a href="https://material-ui.com/demos/text-fields/">Material-UI</a></p><p>React Native: <a href="https://callstack.github.io/react-native-paper/text-input.html">Paper</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f029b3b38020" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Material Studies: Bottom Navigation]]></title>
            <link>https://medium.com/@brianisrighthere/material-studies-bottom-navigation-4bfb88145b19?source=rss-1645b992d23a------2</link>
            <guid isPermaLink="false">https://medium.com/p/4bfb88145b19</guid>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Brian Smith]]></dc:creator>
            <pubDate>Fri, 12 Oct 2018 15:57:14 GMT</pubDate>
            <atom:updated>2018-10-12T16:53:47.130Z</atom:updated>
            <content:encoded><![CDATA[<blockquote><em>This document references content directly from the Material Design Documentation. To learn more, go to: </em><a href="https://material.io/design/components/bottom-navigation.html#usage">https://material.io/design/components/bottom-navigation.html#usage</a></blockquote><blockquote><em>Intended for training purposes at FullStack Labs only.</em></blockquote><h3>Usage</h3><p>Bottom navigation bars display three to five destinations at the bottom of a screen. Each destination is represented by an icon and an optional text label. When a bottom navigation icon is tapped, the user is taken to the top-level navigation destination associated with that icon.</p><h4>Bottom navigation should be used for:</h4><ul><li>Top-level destinations that need to be accessible from anywhere in the app</li><li>Three to five destinations</li><li>Mobile or tablet only</li></ul><h4>Bottom navigation shouldn’t be used for:</h4><ul><li>Single tasks, such as viewing a single email</li><li>User preferences or settings</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*abf-8U7ts2-ZAFpx.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*FJ1u2C0xn0SRNclv.png" /><figcaption>Don’t use a bottom navigation bar for fewer than three destinations (use tabs instead). Don’t use more than five destinations. For those cases, try tabs or a navigation drawer.</figcaption></figure><h3>Anatomy</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*AbanFBMI7zDNGybG.png" /></figure><ol><li>Container</li><li>Inactive icon</li><li>Inactive text label</li><li>Active icon</li><li>Active text label</li></ol><h3>When to Use Labels</h3><p>The way bottom navigation destinations are represented can depend on how many are used:</p><ul><li><strong>Three destinations:</strong> Display icons and text labels for all destinations.</li><li><strong>Four destinations:</strong> Active destinations display an icon and text label. Inactive destinations display icons, and text labels are recommended.</li><li><strong>Five destinations:</strong> Active destinations display an icon and text label. Inactive destinations use icons, and use text labels with caution (as space may not permit them).</li></ul><p><strong>Bottom navigation destinations always include an icon. It’s best to pair icons with text labels, especially if the icon doesn’t have obvious meaning.</strong></p><h3>Label Requirements</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*13d9sF2SAWaw-4PQ.png" /><figcaption>Use short text labels.</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*O_9D_yM2IHvtAssh.png" /><figcaption>Don’t truncate text. The truncation may obscure important destination information.</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*z_qi17sFd_gFtCfJ.png" /><figcaption>Don’t shrink text to fit on a single line.</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*NxepU98yzkh0ZsPI.png" /><figcaption>Avoid wrapping text.</figcaption></figure><h3>States</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Dz7gDcwGKsfw5x1J.png" /></figure><ol><li>Inactive destinations</li><li>An active destination</li></ol><h3>No Scrolling</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*jtc9p76Rf0Z-Smri.png" /><figcaption>Bottom navigation bar destinations don’t scroll.</figcaption></figure><h3>Bottom navigation actions</h3><p>Tapping a bottom navigation destination results in one of the following:</p><ul><li>It takes the user to the screen associated with it</li><li><a href="https://storage.googleapis.com/spec-host-backup/mio-design%2Fassets%2F1-Y09wDWkBCQtc96nxBzY-e0c34Aok4Dl%2Fbottomnav-icons-1a.mp4">On a visited section, it returns the user to their previous scroll position there</a></li><li><a href="https://storage.googleapis.com/spec-host-backup/mio-design%2Fassets%2F10oRw3R7ravU4WRNIhoP0Jal_GmJetnzg%2Fbottomnav-icons-2a.mp4">On the current section, it scrolls the page back to the top and may refresh it</a></li></ul><p>Bottom navigation destinations don’t:</p><ul><li>Open menus or dialogs</li></ul><h3>Badges</h3><p>Bottom navigation icons can include badges in their upper right corner. These badges can contain dynamic information, such as a number of pending requests.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*s88_Wt4fgUQrsq1s.png" /></figure><ol><li>Badge</li><li>Badge with a number</li><li>Badge with a maximum character count</li></ol><h3>Scrolling &amp; Transitions</h3><ul><li><a href="https://storage.googleapis.com/spec-host-backup/mio-design%2Fassets%2F1i9Bgvs2vzCMkB3xtehQ37j8ktbCIZbI6%2Fbottomnav-scrolling-1b.mp4">The bottom navigation bar can disappear to allow more space for content.</a></li><li>Swipe gestures do not navigate between bottom navigation views. <a href="https://storage.googleapis.com/spec-host-backup/mio-design%2Fassets%2F1ubytUIxpk5Cqf-sXElJulE0yQhJZMBpn%2Fbottomnav-scrolling-do-1a.mp4">Transition between active and inactive views using a cross-fade animation.</a></li><li><a href="https://storage.googleapis.com/spec-host-backup/mio-design%2Fassets%2F1n95-I3p0mwuaNhiHQfea4MUwjIzUmn1L%2Fbottomnav-keyboard-1b.mp4">Bottom navigation can be temporarily covered by bottom sheets, navigation drawers, and keyboards.</a></li></ul><h3>Components</h3><p><a href="https://material-ui.com/demos/bottom-navigation/">React</a></p><p><a href="https://callstack.github.io/react-native-paper/bottom-navigation.html">React Native</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4bfb88145b19" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Material Studies: Buttons]]></title>
            <link>https://medium.com/@brianisrighthere/material-studies-buttons-69ca067eed62?source=rss-1645b992d23a------2</link>
            <guid isPermaLink="false">https://medium.com/p/69ca067eed62</guid>
            <dc:creator><![CDATA[Brian Smith]]></dc:creator>
            <pubDate>Fri, 05 Oct 2018 17:01:27 GMT</pubDate>
            <atom:updated>2018-10-05T17:01:27.548Z</atom:updated>
            <content:encoded><![CDATA[<blockquote><em>This document references content directly from the Material Design Documentation. To learn more, go to: </em><a href="https://material.io/design/components/buttons.html#"><em>https://material.io/design/components/buttons.html#</em></a></blockquote><blockquote><em>Intended for training purposes at FullStack Labs only.</em></blockquote><h3>Usage</h3><p>Buttons communicate actions that users can take. They are typically placed throughout your UI, in places like:</p><ul><li>Dialogs</li><li>Modal windows</li><li>Forms</li><li>Cards</li><li>Toolbars</li></ul><h3>Types</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*d4BrWSysBETz0dv5.png" /></figure><ol><li><strong>Text button</strong> (low emphasis)<br>Text buttons are typically used for less important actions.</li><li><strong>Outlined Button</strong> (medium emphasis)<br>Outlined buttons are used for more emphasis than text buttons due to the stroke.</li><li><strong>Contained button</strong> (high emphasis)<br>Contained buttons have more emphasis, as they use use a color fill and shadow.</li><li><strong>Toggle button</strong><br>Toggle buttons group a set of actions using layout and spacing. They’re used less often than other button types.</li></ol><h3>Emphasis</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*1DawyXV6DFC3DT11.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*8g6Hzh_pmyopRsfH.png" /></figure><p>This screen layout uses:</p><ol><li>An extended floating action button for the highest emphasis</li><li>A contained button for high emphasis</li><li>A text button for low emphasis</li></ol><h3>Text Wrapping</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/720/0*C9dxFsYDOr-7u53-.png" /><figcaption>Don’t wrap text. For maximum legibility, a text label should remain on a single line.</figcaption></figure><h3>Placement</h3><h4>DO</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/720/0*uoxSy_p_Hjl9odkQ.png" /><figcaption>In a bottom bar, when using multiple buttons, indicate the more important action by placing it in a contained button (next to a text button).</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*OX-t44ZCQ29xncth.png" /><figcaption>Use a contained button in a bottom sheet next to other important details.</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/720/0*JnsPFBtKfWaKNW8i.png" /><figcaption>In a bottom bar, when using multiple buttons, you can place a outlined button (medium emphasis) next to a contained button (high emphasis).</figcaption></figure><h4>DON’T</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/720/0*uB-SjUffcXHn8Qou.png" /><figcaption>Avoid using two contained buttons next to one another if they don’t have the same fill color.</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*gUf8cN6NyRE3fecp.png" /><figcaption>Don’t place a button below another button if there is space to place them side by side.</figcaption></figure><h3>Text Labels</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/720/0*jnUsROw39CykOI1v.png" /><figcaption>Text labels should be concise and use only the verb if possible. Above is a bad example</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/720/0*wOKShD_61zbn5HcE.png" /><figcaption>Text labels need to be distinct from other elements. If the text label isn’t capitalized, it should use a different color, style, or layout from other text.</figcaption></figure><h3>States</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*k4fDkCFemEGgkeHn.png" /><figcaption>Text Button States</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*ALD0hVoIKBHbVLfC.png" /><figcaption>Outline Button States</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*1r9Zn_jQyis8886A.png" /><figcaption>Contained Button States</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*JzjX1nsek5G0h-AL.png" /><figcaption>Toggle Button States</figcaption></figure><h3>Specs</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/630/1*MEb9kcvv6mSd_kn5AcGfSQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/624/1*qAgajBA6vaWl3cICFzJlIw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/648/1*ZvxD1HIFskZfozDOw-GhSg.png" /></figure><h4>Sizes</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/676/1*jK0CI8GesgOgl8W0mxhpNw.png" /></figure><p>Small: 32px High<br>Medium: 36px High<br>Large: 40px High</p><h3>Components</h3><p>React Native: <a href="https://callstack.github.io/react-native-paper/button.html">https://callstack.github.io/react-native-paper/button.html</a><br>React: <a href="https://material-ui.com/demos/buttons/">https://material-ui.com/demos/buttons/</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=69ca067eed62" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[It’s Not Steve’s Fault — Miss Universe Card Redesign]]></title>
            <link>https://medium.com/way-to-go-champ/it-s-not-steve-s-fault-miss-universe-card-redesign-c5175c0ea4a1?source=rss-1645b992d23a------2</link>
            <guid isPermaLink="false">https://medium.com/p/c5175c0ea4a1</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[miss-universe-2015]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Brian Smith]]></dc:creator>
            <pubDate>Tue, 22 Dec 2015 17:32:07 GMT</pubDate>
            <atom:updated>2015-12-22T17:40:45.075Z</atom:updated>
            <content:encoded><![CDATA[<p>Steve Harvey had the misfortune of being a victim of terrible design on live television in front of (probably) 50 million viewers (I didn’t take the time to Google it). Due to the very, very poor design of the Miss Universe 2015 show finals announcement card, Steve crowned the wrong winner of the Miss Universe title.</p><p>Let’s have a look at why the super awkward situation wasn’t entirely his fault. This is a screenshot of the card Steve was given to announce the winner.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1005/0*V87tueUFEX7AfUuw.jpg" /></figure><p>Would you just look at it? Terrible. So many things went wrong here. Applying just a few basic design principles could have prevented this whole debacle; starting with color.</p><h3>Color</h3><p>By simply changing the “losers” to red, and the “winner” to green, Steve would have easily seen which beautiful lady won the title (assuming he isn’t red/green colorblind). It looks as though the country names are stickers placed on the cards, so we didn’t change the color of those.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/504/0*Leu4ow81QjL8SWSQ.png" /></figure><h3>Positioning</h3><p>How about that positioning though? Why on earth would the designer put the most important name/title at the bottom of the card? Perhaps that’s how the judges’ scorecards appear; I don’t know. Regardless, the designer needs to keep the user in mind. In this case, the user is our friend Steve Harvey and the positioning needs to address his needs and knowledge. Let’s go ahead and fix that too.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/504/0*Tpc01zwN84R03uT7.png" /></figure><h3>Hierarchy</h3><p>There isn’t much hierarchy to the card either. Some minor tweaks and printing two sets of stickers — one large and one small (I’m sure they can afford it) — would have drastically reduced Steve’s likelihood of messing it up.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/504/0*V6q_qpVct0eDUnzq.png" /></figure><h3>Language</h3><p>The wording of the whole thing is pretty confusing isn’t it? At least to those of us who aren’t totally entrenched in the pageant world. It’d probably be helpful to put additional context to the titles.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/504/0*POOeGbQBGZiG4Cbz.png" /></figure><h3>Flair</h3><p>Finally, we all know reading is hard, especially when there’s a lot of pressure to get it right. So, let’s throw a couple icons on there to make it impossible for poor Steve Harvey to embarrass himself.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/504/0*VqAt82Z6oZ0eR05l.png" /></figure><p>We’d like to thank Steve Harvey and the Miss America Pageant for giving us this opportunity to share some of our design knowledge with our friends and family. Without them, we wouldn’t be writing this post. God bless you, and feel free to use these tips when designing next year’s announcement cards.</p><p><em>Header Image Copyright © 2015 by The Associated Press. All Rights Reserved.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c5175c0ea4a1" width="1" height="1" alt=""><hr><p><a href="https://medium.com/way-to-go-champ/it-s-not-steve-s-fault-miss-universe-card-redesign-c5175c0ea4a1">It’s Not Steve’s Fault — Miss Universe Card Redesign</a> was originally published in <a href="https://medium.com/way-to-go-champ">Way To Go, Champ.</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[It doesn’t cost a fortune to have great stock photos]]></title>
            <link>https://medium.com/way-to-go-champ/it-doesn-t-cost-a-fortune-to-have-great-stock-photos-30c90400b9b7?source=rss-1645b992d23a------2</link>
            <guid isPermaLink="false">https://medium.com/p/30c90400b9b7</guid>
            <category><![CDATA[stock-photos]]></category>
            <category><![CDATA[photography]]></category>
            <dc:creator><![CDATA[Brian Smith]]></dc:creator>
            <pubDate>Tue, 27 Oct 2015 23:41:53 GMT</pubDate>
            <atom:updated>2015-10-27T23:41:53.738Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IlfSt-Qz9Kv8vXFL35rnyg.jpeg" /></figure><p>Compelling imagery is essential to drawing customers into your product or service. People make snap judgements — in fact, you only have eight seconds to <a href="http://time.com/3858309/attention-spans-goldfish/">capture their attention</a> — and if the header photo on your website looks dated, cheesy, or irrelevant, they’re going to bail immediately. Also, having great imagery plays a big role in helping customers identify with your brand.</p><p>You want your imagery to speak to your customer. They should feel a sense of <a href="http://www.abelandcole.co.uk/">belonging</a> (“I want to be part of this community”), <a href="https://www.marinelayer.com/">desire</a> (“If, I use this product, I’ll have a life like that”), or <a href="http://www.toms.com/">empathy</a> (“If I contribute, I’ll help that person”). Keep your core audience in mind and select images that are relevant to them.</p><p>When selecting photos for your projects, you have a few options:</p><ol><li>Steal images from the internet. After all, the internet is huge and who will ever find out? (Just kidding, that’s a terrible idea, and <a href="http://www.isba.org/ibj/2014/11/lawpulse/yourclientgotgettyimagesdemandlette">there are bots</a> looking for careless, cheap, and naive individuals just like you.)</li><li>Pay a photographer to take custom images just for you. This can be a great option if you need very specific product shots or coverage of an event. However, expect to pay $500+ for any custom photography.</li><li>Use stock photos.</li></ol><p>Until recently, stock photos were either really bad or really expensive. Luckily, times have changed. There’s a wealth of great stock photo resources out there that are either free or cheap — you just have to know where to look.</p><p>Here are the free stock photo resources we occasionally use when mocking up projects:</p><ul><li><a href="https://stocksnap.io/">stocksnap.io</a> — Wide variety of images.</li><li><a href="http://fancycrave.com/">fancycrave.com</a> — Two new images released every day, along with downloadable photo packs by theme.</li><li><a href="https://unsplash.com/">unsplash.com</a> — 10 new photos every 10 days. Focuses mostly on travel photos.</li><li><a href="http://negativespace.co/">negativespace.co</a> — 20 new photos every week. Has a wide variety of images sortable by type.</li><li><a href="http://www.lifeofpix.com/">lifeofpix.com</a> — Great source for photos of people and animals.</li><li><a href="http://images.superfamous.com/">images.superfamous.com</a> — One of the few places for abstract aerial photos.</li><li><a href="http://nos.twnsnd.co/">nos.twnsnd.co</a> — Vintage photos from the public archive.</li><li><a href="http://jaymantri.com/">jaymantri.com</a> — Artistic landscape and architecturale images from Jay Mantri.</li><li><a href="http://www.gratisography.com/">gratisography.com</a> — Tons of great portraits from Ryan McGuire</li></ul><p>Even though the free stock resources are really fantastic, sometimes you need to search for something more specific. Here are a few options for stock photo subscriptions that we consider to have the best value:</p><h4><a href="http://stock.adobe.com/">Adobe Stock</a></h4><p>$29.99/Month for Creative Cloud Members ($49.99 for non-members) Includes 10 images per month and $2.99 for each additional Image.</p><h4><a href="http://www.shutterstock.com/">Shutterstock</a></h4><p>$169/Month Includes 350 images per month</p><h4><a href="http://www.istockphoto.com/">iStock Photo</a></h4><p>$166.58/Month Includes 750 images per month (Limited to istockphoto “Essentials” collection)</p><p>Nothing beats having an amazing photographer come out and capture the perfect images for you, but if you can’t afford that or time doesn’t permit it, do yourself a huge favor and use great stock images. Finally, keep these three tips in mind when selecting your photos:</p><ol><li>Use the right image size. Never, ever, put a photo on your website that is pixelated, or enlarged past the point it was intended for.</li><li>Choose photos that relate. Select photos that your target audience can identify with.</li><li>Don’t use the wrong photo. Simply put, if you think the photo isn’t right, keep looking. It’s much better to wait to launch your website with the right photos than it is to make a bad first impression.</li></ol><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=30c90400b9b7" width="1" height="1" alt=""><hr><p><a href="https://medium.com/way-to-go-champ/it-doesn-t-cost-a-fortune-to-have-great-stock-photos-30c90400b9b7">It doesn’t cost a fortune to have great stock photos</a> was originally published in <a href="https://medium.com/way-to-go-champ">Way To Go, Champ.</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>