<?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 Mobile Design Guy on Medium]]></title>
        <description><![CDATA[Stories by Mobile Design Guy on Medium]]></description>
        <link>https://medium.com/@mobiledesignguy?source=rss-504b5e6de194------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*6bpwCRwiG2gl6-aERpxpFw.png</url>
            <title>Stories by Mobile Design Guy on Medium</title>
            <link>https://medium.com/@mobiledesignguy?source=rss-504b5e6de194------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 23:13:02 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@mobiledesignguy/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[Expansion Panels…Are They Gone From Material Design?]]></title>
            <link>https://medium.com/@mobiledesignguy/expansion-panels-are-they-gone-from-material-design-18b278fb6b3?source=rss-504b5e6de194------2</link>
            <guid isPermaLink="false">https://medium.com/p/18b278fb6b3</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[android]]></category>
            <category><![CDATA[android-app-development]]></category>
            <category><![CDATA[android-apps]]></category>
            <category><![CDATA[material-design]]></category>
            <dc:creator><![CDATA[Mobile Design Guy]]></dc:creator>
            <pubDate>Wed, 08 Aug 2018 00:11:35 GMT</pubDate>
            <atom:updated>2018-08-08T00:11:35.217Z</atom:updated>
            <content:encoded><![CDATA[<p>Something that almost every designer uses at some point or another regardless if it’s web or mobile design, is Expand/Collapse, right? Native Android App Design is no different and for years with Google Material 1.0 we had the Expansion Panel Component. Now with Google Material 2.0 completely wiping 1.0 from existence that component is gone or is it?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/356/1*mdAESQWjTEJxwe5bK-qy-w.png" /><figcaption>Material 1.0 Expansion Panel Example</figcaption></figure><p>If you’ll remember Expansion Panels were elaborate and the only thing used by and large was the expand and collapse part of them. The fact that you could expand and put editable fields in them and a host of other things was just fluff. So Google did the right thing and nixed the Expansion Panels. When they did this I had Creative Directors and even designers come to me and say “what are we going to do now in Android for expand/collapse?”. Oh still your heart my awesome designer friends, it’s not gone, just refined and moved. Now Expand/Collapse lives under List Component. Rightfully so as it’s the only place this is used and it now is simplified to what 99% of designers, and business for that fact, use it for. To expand and show more information and hide noise.</p><p>If you go to the new Google Material website (material.io) and look under Design &gt; Components &gt; List, you’ll find the Expand/Collapse section. You’ll also find this in their new Sketch Plugin and Material Baseline UI Kit which is extremely useful for designing awesome native apps in Sketch. Also they give a much clearer example in Material 2.0 of how to use this design element and function for your Android native app.</p><p>I know this is short but there really isn’t a lot around this component that is new or old. But it has been a source of confusion for people I know, so I wanted to write about it and put your fears at ease if you thought you were going to have to figure out a new way to do this or not be able to do it at all. It works the same and has the same icon, specs, metrics, etc… Go forth and conquer and keep designing with excellence!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/785/1*RFc8DpwG5OVx3NA066F1_g.png" /><figcaption>Material 2.0 Expansion Panel Expand/Collapse Example</figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=18b278fb6b3" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to do Expand/Collapse in your Native iOS iPhone/iPAD App]]></title>
            <link>https://medium.com/@mobiledesignguy/how-to-do-expand-collapse-in-your-native-ios-iphone-ipad-app-b3b83764c12d?source=rss-504b5e6de194------2</link>
            <guid isPermaLink="false">https://medium.com/p/b3b83764c12d</guid>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[ui-design]]></category>
            <category><![CDATA[ios-app-development]]></category>
            <category><![CDATA[ios]]></category>
            <category><![CDATA[ios-apps]]></category>
            <dc:creator><![CDATA[Mobile Design Guy]]></dc:creator>
            <pubDate>Tue, 07 Aug 2018 00:44:24 GMT</pubDate>
            <atom:updated>2018-08-07T00:48:05.214Z</atom:updated>
            <content:encoded><![CDATA[<p>I wanted to write this blog post because without studying Apple’s HIG very closely and digging into the Apple apps to see a pattern form, it is hard to find much written on this simple yet powerful element that is used on Web and even Native Android. It’s the ability to give your user information and a way to expound on that information by expanding to see more and collapsing to see less.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/615/1*Qg5KLJ-3rhfGB95x_caCDw.png" /><figcaption>Example with FAQs (See Video Below)</figcaption></figure><p>So the question is, how do you do this in truly native iOS app? What does the user expect from their mental models and learned behavior? This is what I’m going to answer here and why.</p><p>A lot of designers out there, especially new to native mobile app design, will just assume that expand/collapse is a common old as the web approach that just works and that it’s the right way to do this because what else are you going to do, right? This is why I created this blog and why I write blog posts and do the youtube channel. It’s because Native Mobile App Design is a completely new thing by and large to designers and a lot of them don’t even know this simple fact. They think it’s like tackling any other design project. I want to you to retain your User Center Design hat and deserve it haha.</p><p>So if Android and the Web have Expand and Collapse, surely iOS does as well, right? I mean it’s just a standard thing, right? Actually, there is no component, and it is not a design element used in the standard sense of the word in iOS Native Apps. There is a very solid establish pattern, an expected behavior by the user that is pretty foundational to iOS Apps. So what is it, it’s the almighty Apple chevron. Let me break it down like this and I’ll show you a video of it in action.</p><p>In iOS Native apps, the way you show a user more information such as an FAQ Answer is to allow them to click on the item they want to know more about and take them (slide them) over to a new page with a back chevron for them to “expand” and read/see more. They can then return and repeat the process for any items they want to dig down into. I know I know your first gut reaction is opinion or maybe in possibly a little frustration at extra work… but remember this blog, this posting, is for how to do native mobile app design the right way. This is the expected behavior for the user. To them it is the least amount of friction and effortless almost without thought, they will perform this action, get what they need and move on either in the app or in the flow. If you are an iOS user you do this a ton throughout the day but it’s such a strong learned behavior and expected behavior in your mental model that you do this without even conscious thought. This is why it is VITAL to design your apps to the users’ native experience and environment. Otherwise, you are designing something that you ‘feel’ is right but is actually causing the user friction and frustration and breaking this rule cost you, the business and ultimately the user.</p><p>I know this is a short article but I hope that it helps you, as you are designing and wanting to design with excellence for your users, to design this the right way for your iOS app customers. The details really do matter even small ones like this.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FGaUKU_rukOY%3Ffeature%3Doembed&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DGaUKU_rukOY&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FGaUKU_rukOY%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/49bbfe61f6581602c9fecc3a247ce9a3/href">https://medium.com/media/49bbfe61f6581602c9fecc3a247ce9a3/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b3b83764c12d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How To Handle Long List Selection in Android/Material Native Apps]]></title>
            <link>https://medium.com/@mobiledesignguy/how-to-handle-long-list-selection-in-android-material-native-apps-4aead3ef9d08?source=rss-504b5e6de194------2</link>
            <guid isPermaLink="false">https://medium.com/p/4aead3ef9d08</guid>
            <category><![CDATA[ui-design]]></category>
            <category><![CDATA[material-design]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[android-apps]]></category>
            <category><![CDATA[mobile-apps]]></category>
            <dc:creator><![CDATA[Mobile Design Guy]]></dc:creator>
            <pubDate>Wed, 01 Aug 2018 03:15:33 GMT</pubDate>
            <atom:updated>2018-08-03T21:32:47.365Z</atom:updated>
            <content:encoded><![CDATA[<h3>How To Handle Long List Selection in Your Android Design</h3><p>In this post we’ll look at some Don’t’s and some Do’s for the best way to handle Long List Selections in a Native Android App. Material is very vague on this but if you go to the phone either Pixel or other phones like Samsung S8, you’ll see a pretty strong pattern established on how best to handle this to keep the user experience the best and to keep your user focused on the task they want to complete fast and get back to the next step.</p><p><strong>The Wrong Way</strong><br>First let’s look at Material Design website and what they say. If you only look at the website, you’ll think you can do more web stuff in a native app such as autocomplete dropdown menus (aka typeaheads) or, dropdown menus with a long list that the user scrolls through. But if you go to the phone and look, you’ll see this isn’t really used for longer list that contain more than 6–10 items. There’s a better way on small glass to do this. (<a href="https://material.io/guidelines/components/text-fields.html#text-fields-layout">Reference Link</a>)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/784/1*g8LUm1SIJc_MnGAc3bDXcg.png" /></figure><p><strong>The Right Way</strong><br>Next let’s look at Android OS native apps and how they handle long list and what the established pattern is for users on this platform are. It’s a mix of Search and List. The user click on (touches) a tile and go to a new page that has a list of items to scroll through, for example countries or states. They can either search (autocomplete) reducing the number of items shown to narrow their selection or just scroll and click on the item they want. This then returns them to the previous screen showing the item selected inside the tile. They can always click on it at anytime to go back and forth, but now they are focused on their task. You can find this in Calendar, Gmail, and several other apps.</p><p><a href="https://164th.net/2ridWKk">View Prototype Here to see it and touch it</a> (Also see video below)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*tu-v8F5YUeDE5wUc.png" /></figure><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FVNv1pJvkfmw%3Ffeature%3Doembed&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DVNv1pJvkfmw&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FVNv1pJvkfmw%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="640" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/9f6d8e4b158be12b8dcd92a6cd1997ae/href">https://medium.com/media/9f6d8e4b158be12b8dcd92a6cd1997ae/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4aead3ef9d08" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How To Design For App Crashes?]]></title>
            <link>https://medium.com/@mobiledesignguy/how-to-design-for-app-crashes-a60b0b7e7072?source=rss-504b5e6de194------2</link>
            <guid isPermaLink="false">https://medium.com/p/a60b0b7e7072</guid>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Mobile Design Guy]]></dc:creator>
            <pubDate>Wed, 01 Aug 2018 03:06:21 GMT</pubDate>
            <atom:updated>2018-08-01T03:07:13.720Z</atom:updated>
            <content:encoded><![CDATA[<p>It seems a lot of people and by people I mean, designers, developers, and even business managers forget how to handle things for the user when things go wrong, seriously wrong. This is another huge part of experience even if it is an edge case that very few users experience, well, if your app is worth anything at all.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/871/1*NHY2JDh1_zioPjcIWrBrQg.png" /></figure><p>Now there is one way to handle this regardless if your app is hybrid, native or native using some HTML wrapped pages. As you know if you read any of my stuff and any serious app designers writings, you’ll know that you should ONLY be doing full native apps with very few exceptions. It’s just a better experience for the user and I will do a post on this to dig in deeper for those who question what is better.</p><p>So here is how to handle app crashes so that the user is handled through the process and understands what is going on. This is really simple which is why I can’t understand why some high profile apps miss this and certainly a lot of new apps. Bottom line is you do not want to leave your user with a crash report or a dead app. You want to get them back to somewhere that they can pick back up or start again and message them gently that something went wrong and please start again. DO NOT, I repeat, DO NOT tell the user your app crashed.</p><p>Here is a design example of one way to handle this, which I do not recommend. Using a standard Google Material/Android Dialog with simple messaging. At least put a RETRY Flat Button instead of OK for the user to try again to see if it’s working.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*07jJ7Li0R4z8Asl1MKkPBg.png" /></figure><p>Here is a better way to handle it more natively and allows the user clearer instructions on how to proceed. Use a snackbar to gently let the user know there is an issue and a way to RETRY whatever they are in the middle of trying to do. Keep it simple. Below is an example of 1.0 and 2.0 of Google Material Design Snackbars with action button. Below is a design example and a sketch file to help you get started.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XSUhrsDuP4xC8-6GwkWing.png" /></figure><p>I hope this helps and I hope it makes things better for your users.</p><p>Download sketch file sample available on blog</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a60b0b7e7072" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Android How To Handle No Data Connection In Your Native Design]]></title>
            <link>https://medium.com/@mobiledesignguy/android-how-to-handle-no-data-connection-in-your-native-design-bf3c5e5dfbd0?source=rss-504b5e6de194------2</link>
            <guid isPermaLink="false">https://medium.com/p/bf3c5e5dfbd0</guid>
            <category><![CDATA[material-design]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[mobile-app-design]]></category>
            <category><![CDATA[android-apps]]></category>
            <category><![CDATA[android-app-development]]></category>
            <dc:creator><![CDATA[Mobile Design Guy]]></dc:creator>
            <pubDate>Wed, 01 Aug 2018 02:19:03 GMT</pubDate>
            <atom:updated>2018-08-01T02:19:03.760Z</atom:updated>
            <content:encoded><![CDATA[<p>So I’ve searched high and low and not found anyone who has addressed this and really thought it through from both a native and Material Design perspective. I had to solve this issue recently and wanted to share with you all what I did. I hope it helps you guys. I’m also going to include the Sketch File so you can download it and use it quickly and modify it to your needs.</p><p>There are going to be times when a user loses connection and you do not, I repeat, DO NOT! leave your user with a dead app. This means they can click on stuff but without any data/internet/wifi connection it just goes no where. Either it spins or if it’s a hybrid or web page wrapped, it could even show, wait for it… a 404 error page. NO!!!! Make sure you account for this and give the user the option to retry to test for a connection and if it is a full page error where they’ve lost connection in the middle of something or on the way somewhere, to show them way to keep going or exit the app. Never leave them with a dead app. I can’t say that enough.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6I4kcF2lzEhanwFwKWH2mA.png" /></figure><p>The designs below keep in mind patterns such as Empty States, Error Patterns and of course the native experience Android users have come to expect and deserve. Even though this particular scenario isn’t called out in Material Design we can still look beyond specifics to patterns and components and piece it together to keep it NATIVE.</p><p>Feel free to change the icon out, but everything else should stay the same. Your Full page version should have a Title of ‘No Data Connection’ or ‘Oops! You Don’t Have Internet’ something that signals the user what happened. It could also be the Tile of the page they were suppose to see such as ‘Terms and Conditions’. On the Dialog the Title in the App Bar should be whatever page they were on before their data was lost prompting the dialog to show. You have two options for dialog; one with a title and one without. It’s design decision that you can make based on what you feel is right for your flow and designs.</p><p>Download samples available on my blog</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bf3c5e5dfbd0" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Full-Width Text Field Inputs for Android App Design (Google Material)]]></title>
            <link>https://medium.com/@mobiledesignguy/full-width-text-field-inputs-for-android-app-design-google-material-2d1279b63f74?source=rss-504b5e6de194------2</link>
            <guid isPermaLink="false">https://medium.com/p/2d1279b63f74</guid>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Mobile Design Guy]]></dc:creator>
            <pubDate>Mon, 30 Jul 2018 18:20:07 GMT</pubDate>
            <atom:updated>2018-08-04T23:24:04.610Z</atom:updated>
            <content:encoded><![CDATA[<p>There’s a lot of silence and confusion around this topic for a lot of designers who are tasked to design native Android apps for their companies or friends even. Especially new mobile app designers who solely rely on Google Materials website without ever picking up an Android OS phone and experiencing the platform first hand. This is why you see a lot of variations and rouge text inputs and inputs in general in all apps. That’s why this article will take a deeper dive into the right way to do you text inputs in your Android app and why. I’ll also show you different states so you know how to handle those correctly. Ready? Here we go!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/358/1*cZBJImEGbcVBhlEAhOzyPA.png" /><figcaption>Full-Width Text Fields for Android Native App Design</figcaption></figure><p><strong>The Wrong Way</strong><br>Now at first glance looking solely at <a href="https://material.io/guidelines/components/text-fields.html">Google Materials Website</a>, you’ll think text fields should be done as what they call, floating text input fields. WRONG!!! Pick up a phone and even bad apps that don’t follow Material and Google apps don’t follow this. Example shown below is Gmail, Calendar, Contacts, etc… This is more web and not a native app. The user may not consciously be aware of this or be able to call it out, but they will FEEL it and sub-consciously know something isn’t right. Come on? Even you have opened up an app and just have this nagging feeling that something is right, right?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/784/1*g8LUm1SIJc_MnGAc3bDXcg.png" /></figure><p><strong>The Right Way</strong><br>Anyone who has used a smartphone either Android or iPhone knows what a native text input field is. It’s instinctual at this point. It’s a strong mental model that’s been established since the birth of smartphones. Oddly enough Google Material Design website only has a blurb about it and it’s hard to find much online about it either. I think this is SO Bizarre but as someone who constantly looking to build consistent and good apps for my users, I pick up the Pixel, Samsung S8 and any other Android OS phone I can to experience what is in the real world and not on a website, users will never look at. What did I find? I found Gmail, Google Calendar and so many more. Even apps that don’t follow Material strictly use these Full-Width Text Input Fields. When you see it, I bet you’ll be like OF COURSE!! LOL. Because even iOS uses these. It’s just a strong established pattern. Which is why I’m SHOCKED Google Material Design doesn’t call this out more clearly.</p><p>Other reasons we should only use Full-Width Text Input fields in native Android app designs are:</p><ol><li>It gets really ugly and clunky for the user if you are mixing list tiles with floating text fields, both because floating text fields should never live in a list tile but float on the background (white) and also because it’s confusing to look at with lines showing what you can click on and then other lines to type into that look different. Please, don’t get me started.</li><li>Full-width keeps everything uninformed and thus keeping the user more focused on their task and less overwhelmed. When their eye hits it they feel like it’ll be easy and not complex. It also smoothly let you mix text input fields with selectors, dropdown menus, expansion panels and more which I go into more in other articles and articles to come.</li><li>It’s an established pattern that will reduce friction and frustration on your users. And who doesn’t want that!</li></ol><p><strong>When Not To Use These</strong><br>Currently in Google Material Design 1.0 and 2.0 there is no validation error patterns around full-width text input fields. So I would recommend not using these if you need to validate the users input and produce errors if something is wrong. In this case you should use a floating text input field or now as they are called, filled or outlined per Material Guidelines. This is your call as a designer and you could create error patterns around full-width text fields, but if you do this, please make sure that the user is clear on what is going on and how to proceed. You will be breaking a mental model they are use to and they will have to think for a second to figure out what went wrong and how to fix it. This is why I recommend only using these full-width text fields that you find in Gmail and other Google native apps, when you have no validation.</p><p>I hope this helps! Go design with excellence!</p><p><strong>GMAIL FULL-WIDTH TEXT INPUT FIELD EXAMPLE</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rZbzeoCel0tazye62NZJSA.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2d1279b63f74" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Best Way To Do App Rating On Android]]></title>
            <link>https://medium.com/@mobiledesignguy/the-best-way-to-do-app-rating-on-android-8a0ce603091c?source=rss-504b5e6de194------2</link>
            <guid isPermaLink="false">https://medium.com/p/8a0ce603091c</guid>
            <category><![CDATA[android]]></category>
            <category><![CDATA[material-design]]></category>
            <category><![CDATA[android-apps]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[mobile-apps]]></category>
            <dc:creator><![CDATA[Mobile Design Guy]]></dc:creator>
            <pubDate>Mon, 30 Jul 2018 18:06:03 GMT</pubDate>
            <atom:updated>2018-07-30T18:07:41.318Z</atom:updated>
            <content:encoded><![CDATA[<p>So this is really boring in most apps and usually super annoying. It pops at the worst times asking you if you like the app and to please rate us. Right? I often wonder if they designer or/and business know if I had the time how many 1 star reviews they would get just for this frustrating and complete lack of thought popup in my face. Seriously right in the middle of typing or about to click submit and BOOM! So this blog post is about two things; how to do this app rating right and when to do this app rating right for your app.</p><p>First off this is a HUGE friction point for 99% of your users. They are there to do something in your app and they need/want to do it and get out. Unlike websites, a great experience in an app, is how fast can I accomplish what I need to do and get out most of the time with a few exceptions like Instagram where people come to hang out and browse. But I’m talking about functional apps such as Bank apps, Food delivery, things like Uber, booking a hotel, and on and on I can go, these apps the faster I can use them and accomplish what I needed, the better I feel about the experience. Agree? If yes then we are tracking together. So, how do we ask our users for a rating or even feedback with the least amount of friction? We design it right, simple and most importantly trigger it at the right moments.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FLIn6U_khugI%3Ffeature%3Doembed&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DLIn6U_khugI&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FLIn6U_khugI%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/929d2bc85aa84d5ae166c35774741d57/href">https://medium.com/media/929d2bc85aa84d5ae166c35774741d57/href</a></iframe><p><strong>HOW</strong><br>So you’ll see here a design that makes this experience pleasant, easy to ignore and also simple to do. When users see the same old Android OS dialogs popping up, let’s be honest, this is normally white noise to them. They just want it to go away. I could dig into why here, but let’s just sum it up by saying to primary reason for this, is improper use of dialogs because, again, honestly, it’s the easy way out both for designs, developers and the business. Ok, back on point. The design below is a full page dialog that does stretch the bounds of Material Design mostly because there is nothing specific around it, but as you’ll notice, it does still follow material in many ways keeping the experience native and not web. We easily drive them away from rating if they are unhappy and to us to give feedback and if they are happy to simply rate it, all the while making it feel and actually be very simple, easy and fast.</p><p><strong>WHEN</strong><br>Before we look at the graphics, let’s talk about the WHEN! Right? This is even more important that the look and feel. Don’t let your team or a 3rd party trigger this randomly on a user, that will never give you true results and certainly not happy ones that you can celebrate. Make sure that they are triggering these ask at the right moments. What is the right moment you ask? It is always when the user is feeling good. Simple right? Let me explain. Say you are a hotel and your user just successfully booked a room, they feel good, you know by metrics and algorithms that they did it quickly and you can pretty assuredly feel like they are happy and BOOM, trigger your App Rating request. Making more sense now?</p><p>Now do not trigger it if someone booked the room but you know they’ve been looking for 35–60+ minutes on the app, oh no that’s too risky. Another example is banking, if your user just did a mobile deposit in less than 30 minutes, BOOM trigger your app rating. Bottom line, look for moments, calculated moments, that you can trigger your ask to a 80–90% guesstimate of a happy user. This will yield incredibly higher 4–5 star ratings in the Google Play Store, than randomly frustrating your user. Take the time and budget to do this. People pay attention more than ever to reviews. In a world of Yelp and Google Ratings and Trip Advisor and Amazon and on and on it goes… you will lose $$ and sometimes a lot of money for not paying attention to this. Restaurants know this or should know this, that a 1 star review can not only cost them hundreds if not thousands from the user that placed the bad review and will never return but also countless other people that will not risk it and take their money elsewhere.</p><p>DESIGN EXAMPLE</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*E3T6uEpc6s2-8s52SVcbcQ.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8a0ce603091c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Google Material Design 2.0]]></title>
            <link>https://medium.com/@mobiledesignguy/google-material-design-2-0-b68480b4c16f?source=rss-504b5e6de194------2</link>
            <guid isPermaLink="false">https://medium.com/p/b68480b4c16f</guid>
            <category><![CDATA[android-apps]]></category>
            <category><![CDATA[material-design]]></category>
            <category><![CDATA[google-material-design-2]]></category>
            <category><![CDATA[android-design]]></category>
            <category><![CDATA[android-app-development]]></category>
            <dc:creator><![CDATA[Mobile Design Guy]]></dc:creator>
            <pubDate>Sun, 29 Jul 2018 16:27:05 GMT</pubDate>
            <atom:updated>2018-08-05T15:40:05.829Z</atom:updated>
            <content:encoded><![CDATA[<h3>The Elephant In The Room</h3><p>So April brought the brand new Material Design 2.0 and the death, sudden death with no warning of Material Design 1.0. Designers around the world in flight with their Android App Design projects were stunned with no warning and no way to revert and reference Material Design 1.0. Millions of dollars were spent to build Android Style Guides according to 1.0 and now have very little refuge to reference the core, Material 1.0. Can I also take a moment here to talk about why Google would talk about having faster servers at the I/O but launch Material 2.0 and over a month later every page, even at my 500Mbps speed, is loading like we’re stuck in the 90’s on dial up?? This has to be an embarrassment for Google. Every other new thing they launch, example Gmail, there’s always a way to revert back. Why wouldn’t they follow this ‘pattern’ for Material? Oh and don’t get me started on them being Google and yet every search within google and material for weeks had dead/bad links… WHAT IS GOING ON!!!???</p><p>Below I’m going to call out the primary things that have been removed, added and changed. I won’t go through everything but will hit most of it even if it’s just a call out.</p><p><strong>What’s Been Removed<br></strong>I’ll keep this short but there are some huge impacts here to designers trying to design the best Android/Material Apps for their users.</p><p>Removed</p><ul><li><a href="https://web.archive.org/web/20171228010945/https://material.io/guidelines/components/steppers.html">Steppers</a></li><li><a href="https://web.archive.org/web/20180223140408/https://material.io/guidelines/patterns/confirmation-acknowledgement.html#confirmation-acknowledgement-confirmation">Patterns</a></li><li><a href="https://web.archive.org/web/20180223140409/https://material.io/guidelines/components/pickers.html">Pickers</a></li><li><a href="https://web.archive.org/web/20180223140408/https://material.io/guidelines/components/toolbars.html">Toolbars</a></li><li><a href="https://web.archive.org/web/20180223140410/https://material.io/guidelines/components/lists-controls.html">List Controls</a></li><li><a href="https://web.archive.org/web/20180223140410/https://material.io/guidelines/components/grid-lists.html">Grid Lists</a></li><li><a href="https://web.archive.org/web/20180223140408/https://material.io/guidelines/components/widgets.html">Widgets</a></li><li><a href="https://web.archive.org/web/20180223140409/https://material.io/guidelines/components/snackbars-toasts.html">Toast</a></li></ul><p>Steppers<br>Vanished, they are gone, I say this was a good call as I’ve never seen it used and have no idea why anyone would need to use this. That being said a lot of corporate business persons that do not understand design but think more logical and also think more in terms of bringing web over to apps so that it “looks the same” everywhere, as though users are checking all platforms and devices and comparing them LOL HAHA. But I digress, so I think this was a simple thing that won’t be a huge deal. Also a HUGE removal that I hope will come back is</p><p>Patterns<br>Google WHY? Why would you remove Patterns. This is essential to any guide and designers so that things stay consistent across your app regardless if it’s Android or iOS or Web. You need Patterns for all 3. So this was a huge shock and extremely odd decision. Let’s see, what else is gone…</p><p>Pickers<br>Yes the famous Date picker and Time picker that have been around since possibly back to Android OS 1. iOS has been using spinners since iPhone 1 basically and Android has been using a custom dialog popup called pickers that worked great for most situations. So there are some mentions of this now in Text Fields Components and in Dialog Components, but nothing solid. There is a full-page option shown in an animation video but no real guidelines around when and when not to use this. If you are going to remove a component that is used a lot in various apps, including your own (aka Calendar), why not offer an alternative? Swing and miss… People from Booking sites, to banks, to just about anyone that uses dates and times, need a visual element to display to the user an easy consistent way to select dates and times.</p><p><strong>What’s Been Added<br></strong>So I’ll dive into a lot of this more in depth in other post, but wanted to call these out here so in one post you can see what’s been removed and what’s new. There is some great new stuff and options for designers to help their users and stay consistent with mental models and learned behaviors.</p><p>Net New (Brand New Additions)</p><ul><li><a href="https://material.io/design/components/sheets-side.html">Side Sheets</a></li><li><a href="https://material.io/design/components/navigation-drawer.html#bottom-drawer">Bottom Drawer</a></li><li><a href="https://material.io/design/components/app-bars-top.html">Top App Bar</a> (now a component)</li><li><a href="https://material.io/design/components/app-bars-bottom.html">Bottom App Bar</a></li><li><a href="https://material.io/design/components/banners.html">Banners</a></li><li><a href="https://material.io/design/components/backdrop.html">Backdrops</a></li><li><a href="https://material.io/design/components/image-lists.html">Image Lists</a></li></ul><p>Not Net New but Changed Enough To Mention</p><ul><li><a href="https://material.io/design/components/text-fields.html">Text Fields</a> (huge changes)</li><li><a href="https://material.io/design/components/buttons.html">Buttons</a> (huge changes)</li><li><a href="https://material.io/design/components/sliders.html">Sliders</a></li><li><a href="https://material.io/design/components/snackbars.html">Snackbars</a></li></ul><p><strong>The Good, The Bad, The Ugly, The Beautiful</strong><br>Here I’ll summarize what I like and what I don’t and why.</p><p><strong>The Good The Beautiful</strong><br>There is some really great new stuff in Material 2.0. Buttons are much better defined and give designers a lot more options that work better with ADA across light and dark themes. I do not understand why they had to change the names (design language) because it will cause a learning curve and some confusion as people switch over but the buttons are better with better guidelines. Last but not least, now buttons can have icons. I’m on the fence about this but again, I like designers having options, so we’ll see how they are used both by Google apps and by designers. The addition of the bottom drawer and bottom app bar, I think, offers some really cool options for me as a designer to help my user access things faster and easier when it makes sense in context of the design and goal of that design for the user. I do see an obvious dilemma for those using a bottom navigation, so use common sense and think through your entire flow before using any components. Side sheets, I love when designers have options, although I haven’t dug into this yet, I can see where this could be used and beneficial to the user especially for business/corporate apps where they try to shove everything in the kitchen sink into one app.</p><p>Beyond listing out components, there is some really good new guidelines that makes it clearer not only for designers and devs but also to prove things out to the business on why you designed things a certain way and why you shouldn’t do things they might be asking for. This is a huge win for the user. Anytime we have better guidelines, designs become more consistent and especially, again, across huge apps this is a HUGE win for the user. Some business have over 100 designers working on their Mobile apps for different segments and usually these designers are in various regions and never really meet. For them to all design in a way the user doesn’t feel that, guidelines and common core or/and digital design language systems are a must.</p><p>HINT: <a href="https://play.google.com/store/apps/details?id=com.seven.eleven.phoenix&amp;hl=en_US">Check out 7 Eleven new apps. WOW!! Impressed by the designs and thought into this.</a></p><p>Theming is something new to Material 2.0 and along with that comes a new Sketch Plugin which is really well done and I really like this part of 2.0. It really helps designers design and communicate their design more effectively. I’m looking forward to how this evolves with InVision Studio and even Principle, etc… I think this a really well thought out and beautiful addition to Material Design.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FOkz5kqcAsD4%3Ffeature%3Doembed&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DOkz5kqcAsD4&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FOkz5kqcAsD4%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/3104fb927c58a27fbdd02804cd1dc806/href">https://medium.com/media/3104fb927c58a27fbdd02804cd1dc806/href</a></iframe><p><strong>The Bad The Ugly</strong><br>So I already mentioned this above, and you might see that I’m in a love hate relationship now with Google and Material Design haha, but we have to talk about LANGUAGE and how important it is for communicating across designers, designers to development and back as well as to the business and changing language is never a good idea unless it really drastically improves things. So Google made the BOLD and STUPID decision to change the name of their buttons. UNNECESSARILY!! So not only designers around the world that communicate, but designers within your local teams and of course the always difficult position of communicating to your development team just got harder because for no apparent reason, the buttons in Material are called completely new things. So instead of Raised Buttons which we’ve known since Material 1.0 launch over 4 years ago, so we now have Contained Button (previously Raised) which is no longer using ‘Material’ which included elevations and is flat, which again makes no sense and I do love the new buttons but am questioning some of the decision around them. Flat buttons are now Text buttons (previously Flat). We have the new Outlined Button and of course Toggle which is only used in more web/tablet designs, not small glass. Ok Ok, I’m done with this soap box lol for now ;)</p><p>Worse than making designers, business, developers and everyone in between to learn a new language is the removal of Patterns. HUGE HUGE MISTAKE and HUGE STUPID ERROR!! Everyone knows from UXD and UXA and heck just basic Design 101 from the beginning of design, you need patterns if you care about your users at all. Maybe a small project with one or two designers you can still build out a consistent experience without patterns but it’s impossible in a large company where you constantly have to make your case for design decisions and design thinking and keep things across multiple departments, designers, developers, sometimes even global…consistent. What the heck was Google thinking? Did they really just completely miss this or is it still coming or are they really arrogant enough to think that they can change this? I just don’t know… I’m at a loss…</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zh60-_akFEqt0OJVZzgP3w.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b68480b4c16f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Chevrons In Native Android Apps]]></title>
            <link>https://medium.com/@mobiledesignguy/chevrons-in-native-android-apps-36955564c938?source=rss-504b5e6de194------2</link>
            <guid isPermaLink="false">https://medium.com/p/36955564c938</guid>
            <category><![CDATA[google-material-app]]></category>
            <category><![CDATA[native-app-design]]></category>
            <category><![CDATA[native-mobile-apps]]></category>
            <category><![CDATA[ux-android-design]]></category>
            <category><![CDATA[android]]></category>
            <dc:creator><![CDATA[Mobile Design Guy]]></dc:creator>
            <pubDate>Sun, 29 Jul 2018 02:32:28 GMT</pubDate>
            <atom:updated>2018-08-06T02:11:24.891Z</atom:updated>
            <content:encoded><![CDATA[<p>This for some reason is a huge issue for a lot of business owners, product owners and even UXD/UXA/UXE Designers. I’m not sure why because it’s pretty cut and dry but here we go down into the rabbit hole known as Chevrons or as some people refer to them, side arrows.</p><p>Chevrons, do you put them in your Android native app or not? This is the great and mighty debate raging on especially when it comes to iOS users that are designing Android apps and have rarely or never used and Android Phone. The are probably also new to or don’t even know about Google Material Design. Otherwise there would be no debate.</p><p>iOS/iPhone/iPad/etc… do you use Chevrons or not? The answer is probably more obvious as most designers are iPhone/iOS users and even though many of them don’t know or know very little about the Apple Human Interface Guidelines (HIG), they know what a chevron is because it’s literally everywhere even in Safari and apple’s own website not to mention in their apps, OS, and pretty much anything Apple. So the answer is YES. Use use chevrons which you can see in our simple side by side example below which is a closer look at Instagram who by and large doesn’t always follow standards and yet they did follow this one.</p><p>So, what about Android? The answer is a clear and precise NO! Oh, if only that was enough but I know all to well that this is not a good enough answer for most of you or someone you know, so I will dive into Chevrons and why you should rarely rarely practically never use them in your Native Android App.</p><p>Why don’t we use Chevrons in Android? If you follow all the principles of design, the basic ones, such as following your style guide to create consistency for the user, this alone should be enough. You see Google Material Design and Google Native Apps do not use Chevrons. Most users on Android do not even know what that side arrow does. Can they figure it out, of course they can but if you are trying, really trying, to design an app that is native to that users platform and thus environment, then you have to care for them in foundational ways all the way to the smallest detail. Right? If you disagree then STOP reading, put the blog down, walk away and change careers. Seriously… Ok, if you are still here then you are a great designer, passionate, willing to continue to get better. AWESOME!</p><p>Did you know that if you study it out over 96% of Android users hate Apple. I mean hate them. They never Apple people. They’ve never had one and don’t plan to have an iPhone or iPad. The other percentage have either switched from Apple’s iPhone to and Android Phone or have an Android Phone and also an iPad or Macbook Pro etc… That’s huge right? So if you hate Apple, do you think you’ll be happy seeing “Apple” stuff in your Android apps? You have to take yourself out of the equation. You HAVE to remove your opinion out of the design as much as possible. Be USER FOCUSED!! Put your user first. Design for them.</p><p>This goes both ways, if you are deep into Google Material Design or/and are an Android Phone user, do not put your likes of Android apps into your iOS designs. Why because guess what, yep 98% of iPhone users have never and will never use an Android Phone. They are vastly loyal and could careless about seeing Android OS stuff on their phones. Now this is tricky because Google has a lot of products, and some of them are apps such as Gmail, Google Calendar, Google Maps, etc… that live also on iOS and have departed from Google Material Design very little. That is another blog post but I did not want to miss that fact here as I know some of you will be thinking about it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ai32-tuVs34ZBRQIsxvvKA.png" /></figure><p>A few more points as to why you should not use Chevrons in your Android Native App Designs. Reduce friction for the user, so that they don’t even have to think. For a lot of designers this is tricky because the Chevron naturally shows a user it’s clickable right? WRONG! Only in your iOS world, get out of your head lol. Android has it’s own visual cues to show it’s users what is tappable and what isn’t. Learn it, get into an Android app and use it. Even on your iPhone get into Google apps. Have empathy and understanding for your Android users. Don’t impose your opinion, feelings, iOS design guides, nor web design principles onto them. It’s not good design, it’s not good for the business, it’s not good for their customers. Another reason is adaptation, to reduce a break in learned behaviors and strong mental models. If you introduce new navigation patterns into your design, your user has to burn more calories, stop (friction), think more even if it’s sub-conscious, it will leave them will a feeling that the app is not designed well and even difficult to use. What does this do? It reduces your adaptation and usage. That means business owners, product owners… yep you’ve wasted money, time and effort on something people don’t use or rarely use. And yes, the devil is in the details.</p><p>So in conclusion, bottom line is we don’t use Chevrons in Android apps because they aren’t native components to that platform and do not serve the user natively and reduce consistency from app to app. When a user can pick up an app and it feels and works the same as their other apps, they are more likely to use it, use it more often and feel like it’s easy to use and even fun. I’ve said this before, but I’ll say it again here. Research is great. In fact you can rarely design something amazing with the user center of it all without good solid research and testing. But, and this is a BIG BUT, you never mess with foundational elements, components, patterns, etc… Even if they aren’t the best and need improvement and let’s be honest, nothing on earth is perfect. iOS and Android have much to improve on and are always growing and changing. The reason you don’t mess with these is clear, CONSISTENCY for the user is KING!</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FxF3OKrw-KOM%3Ffeature%3Doembed&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DxF3OKrw-KOM&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FxF3OKrw-KOM%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="640" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/c363b0f6390277011d34079649ae4bec/href">https://medium.com/media/c363b0f6390277011d34079649ae4bec/href</a></iframe><p>When something is core to an app for it’s respective platform, it’s been driven deep into the learned behavior and mental model of your users. They do these things like open their Drawer, Swipe against a tile, hit the CTAs without even a thought in well designed apps because it’s so deeply entrenched that it’s effortless which creates a great experience and serves your customers well. BURN OPINION! Follow Google Material Design the site and most of all look at the apps, that is where your user lives. Not bad apps, not random apps, but apps that follow Material, that adhere to the standards. Remember that Goole has millions and millions of users all over the world as does Apple, that use their apps daily. Millions use it every second. Don’t think for a second that you are so smart you’ll just change some core element, do a little research and testing and shove it down your users throats. It’ll blow up every single time.</p><p>I hope this has been helpful for you guys and that it will allow you to stand behind your good design decisions and teach you new ones to make you a more excellent designer of native mobile apps. Let’s grow together! Be sure and check out the YouTube Channel for more and have a beautiful blessed day!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*B--C-qttAq3_oOgffE8FrA.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=36955564c938" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>