Downloaded 19 times
Uploaded byLori Olson
Mobile rage
The document discusses 'mobile rage,' a frustration experienced by users when mobile applications or websites fail to function properly. With smartphone ownership rising to over one-third in Canada, it highlights why addressing these issues is crucial for user satisfaction and business performance. The text outlines common problem areas and offers suggestions for improving mobile usability through better design and functionality.
More Related Content
![Responsive Design & Beyond [Code & Creativity Workshop]](https://cdn.slidesharecdn.com/ss_thumbnails/codecreativityworkshop1-140506164731-phpapp01-thumbnail.jpg?width=640&height=640&fit=bounds)
Mobile rage
- 1. Mobile Rage Lori Olson The WNDX Group Inc
- 2. Lori Olson • TheWNDX Group Inc • Independent contractor • Used Rails for since 2005 (0.13?) • Mostly oil & gas apps
- 3. Mobile Gadgets • since...Windows CE • Palm/Treo • iPhone/iPad
- 4. Mobile Rage • What is it? • Who experiences it? • Why has it become such a problem? • How do we go about fixing it?
- 5.
- 6. It’s that feelingof intense frustration you experience, when using web applications or web sites from your mobile device, and they JUST DON’T WORK RIGHT.
- 7.
- 11. Overall smartphone ownershipis up by 13% in the past six months in Canada, according to Ipsos Reid. Now, more than one-third of Canadians own smartphones—up from just one quarter in August 2011. - Techvibes http://www.techvibes.com/blog/canadians-loyalty-to-blackberry-vanishes-as-android-and-apple-gain- marketshare-2012-04-20
- 12.
- 13.
- 14.
- 15.
- 18. Problem Areas • Landing •Advertising • Navigation • Forms
- 19.
- 20. Psst! Did youknow your app is slow on mobile?
- 21.
- 22.
- 23. Javascripts • jQuery/UI •could be replaced by Zepto.js • Top loading • Bottom Loading
- 24.
- 25.
- 26.
- 27.
- 28.
- 29.
- 30.
- 36.
- 37.
- 38.
- 39.
- 40. No “Full Site”link
- 41.
- 42.
- 43.
- 45.
- 46.
- 47.
- 48.
- 49.
- 50.
- 51.
- 52.
- 54.
- 55.
- 56.
- 57.
- 64. text_field(:user, :email, :size=> 60) email_field(:user, :email, :size => 60)
- 65.
- 72. text_field(:user, :account_name, :size=> 20) text_field(:user, :account_name, :size=>20, :autocomplete => 'off', :autocapitalize => off)
- 73.
- 74.
- 76. text_field(:user, :home_page, :size=> 120) url_field(:user, :home_page, :size => 120)
- 77.
- 79. text_field(:user, :cell_phone, :size=> 20) phone_field(:user, :cell_phone, :size => 20)
- 80. In retrospect • ThereWILL be more mobile users than not, if you haven’t already got there • Old applications cause lots of rage • Applications inducing mobile rage aren’t good for the bottom line • If you can’t go back & do it the right way, go and do all the little things, because they DO make a difference
- 81. @gorbypuff wants youtoo! thanks @tenderlove
- 82. Thanks! • Lori Olson •@wndxlori • http://wndx.posterous.com • Questions?
Editor's Notes
- #2 \n
- #3 \n
- #4 \n
- #5 \n
- #6 What is Mobile Rage?\nSome people wouldn’t call it rage at all. \nMobile frustrated. Mobile annoyed. Mobile peeved.\n\n
- #7 But I call it Mobile Rage. It’s that feeling of intense frustration you experience, when using web applications or web sites from your mobile device, and they JUST DON’T WORK RIGHT.\n\n
- #8 Just the fastest growing segment of the web consumer market.\n\n\n
- #9 The smart phone users. The tablet users\n\nI’m not talking about dumb-phone users. \n\nI mean, T9 predictive text rage is just a given, so anything on top of that is just superfluous.\n
- #10 \nI mean, T9 predictive text rage is just a given, so anything on top of that is just superfluous.\n
- #11 Here we are, at the inflection point. Smart phone shipments will EXCEED personal computer shipments this year.\n\nhttp://www.webdesignshock.com/responsive-design-problems/\n\n\n
- #12 Seriously. One third. Now that’s a market share you just can’t ignore.\n
- #13 Why are things SO bad? Somehow we got to this point, where so many web sites and web applications invoke so much rage amongst consumers?\n\nHow long has the web been around? I built my first website in late 1994. 18 years ago. How many websites and web applications are relatively static... because they work... good enough?\n\nWell, Rails applications have been developed for around 8 years now. Eight years ago, mobile was just barely on most product radars, and the iPhone *didn’t exist*, except in Steve Jobs secret little world.\n
- #14 So how did WE get here? And how do we fix it?\n\nWell, the answer for us Rails developers is simple isn’t it?\n\nBecause Rails developers only work on greenfield projects, brand NEW web applications\n
- #15 So we just develop these new applications using mobile first.\n\nThis is where you START and I would argue this is where you finish as well. Your application design should work on mobile first, and then you work on the desktop representation.\n
- #16 Responsive design will solve the rest of our problems, won’t it? \n\n
- #17 Our applications adapt to mobile seemlessly and everything is all rainbows and unicorns, right?\n\nBecause we don’t have to support any old applications, that were built and designed before anyone ever heard of mobile first and responsive design. \n\nWe certainly never have to integrate with old applications, or existing CMS systems or anything like that...\n\n
- #18 \nOf course, if you still believe in fairy dust... I can’t help you.\n
- #19 So if we are going to talk about how to fix things, we should probably start with defining the problems.\n\nSo let’s talk about the general classes of problems that induce mobile rage\n
- #20 \n
- #21 Hey, did you know that your web app is slow on mobile?\n\nYa, that’s what I thought.\n
- #22 That’s an alarming statistic\n
- #23 That all adds up to almost 40% of mobile users... that’s not good, is it?\n
- #24 We know that loading Javascripts can be a problem\n\n\n
- #25 Certainly some old sites, where developers have been hacking at them for years, have big, bloated CSS files\n\nI mean, you’re never really sure that removing something won’t break something obscure, right? Much easier to just keep adding to it.\n
- #26 And then of course there are images. With the rush to support iPad retina displays, our images are getting even more bloated than ever.\n
- #27 But wait a minute... javascript, CSS, images.... Don’t we already\nhave a way of dealing with some of this in Rails. The asset pipeline.\n\nNow, that’s all very fine for your new Rails apps, however \n\n\n
- #28 Asset pipeline can be added, just not in the totally integrated fashion that we have now.\n\nBut really, wouldn’t it just be better to use this as another argument in favour of upgrading those old apps?\n
- #29 So, once we get past ts;dw we have to deal with all the different strategies that developers have hacked together for dealing with mobile. Some are older, some are newer.\n
- #30 While it seemed for a while that Flash would survive the iOS onslaught, the sad fact is that Flash is dead on mobile. And when I say sad, I’m not really sad, but I assume there are some Flash developers out there who are sad. \n\nThere is really no excuse at this point for having a Flash-only site, or even a Flash mostly site.\n\nHonestly, the biggest offenders here are restaurants, and other similar enterprises, that just wanted a “web presence”, and hired some agency to build one for them.\n\n\n\n
- #31 \n
- #32 Do nothing. That works for your customers.\n\n
- #33 Provide misleading information... and then do nothing.\n\n\n
- #34 You are viewing this page because your computer/device doesn’t have the Adobe Flash plugin. But you can download and install the plugin by clicking here!\n\n\n\n\n
- #35 Hey, why not insult your web visitor while you’re at it!\n\nhttp://thetoshibatablet.com\n\n
- #36 That’s a nice mobile device you have. Unfortunately, you can’t view your digital edition on this particular mobile device.\n\nThis, while not ideal, is probably the best (least rage inducing) of the bunch.\n\nIn fact, this is a screen capture that my husband took. Not only did it NOT induce rage, but he actually LOL’d\n
- #37 Leaving Flash behind us for the moment, let move on to more of the “do nothing” landing strategies.\n\nThis is probably the option that causes the least amount of rage. The smart mobile browsers can view a lot of web sites and applications, with some issues. But if it mostly works, that’s pretty good.\n
- #38 Some Javascript that checks, determines that your mobile device is not worthy, and and dumps you into the mobile site\n\nBad enough when this is on the homepage, but when you have a link, that could/should take you to the exact page you want, but... the mobile redirect kicks in, and punts you out mobile\n\n\n
- #39 This is a follow on, of the mobile redirect. Already pissed at not being able to get directly to the page you were after, now you discover that the mobile site is\n\n\n\n
- #40 1. a “limited” function version of the full site\n\n
- #41 2. entirely walled off from the full site and you *can’t* get back to the full site.\n\n
- #42 A variation on the “mobile redirect” is the mobile detection FAILURE. \n
- #43 Here I am, on my iPad, but it’s been detected as an iPhone, so I get the squishy, narrow version that works (ok) on the phone, but is exceedingly annoying on the iPad. And, of course, there is a link that will take me to the “Full Site” (all the way at the bottom), but it takes me to the front page of the full site, not the story I was reading.\n\nOk, I think we’ve come full circle here, so lets move on to the\n
- #44 So another landing option is to not bother handling the mobile devices in the web browser at all. Instead, there’s an app for that!\n
- #45 If people don’t WANT your app...\n\nIf they CHOOSE to use your full site...\n\nJust let them!\n
- #46 Make it a default! Save a freaking cookie!\n
- #47 Advertising is, in many ways, the bane of our existence, as consumers of the web.\n\nHowever, as web app developers, we know that there’s money to be made in advertising, so we do it anyway.\n\nBut maybe. since it’s so annoying anyway, we could do it better on mobile...\n
- #48 You know these. Popups. Lightboxes. You’ve never liked them on the desktop. But on mobile, they are even worse. \n\nThe (sometimes) delayed popup version is even worse. You got to a page, you double tapped to zoom in to the text, and BLAM, there’s this annoying popover, covering up the content, and when you try to zoom out, you inevitably, accidentally click on something from the popover, and you are now on a new page. What fun!\n\nA more evil version of this problem, is where the popover is sized so that it extends beyond the edges of your mobile screen, so that you cannot immediately dismiss it. You have to guess... is this the once with the ‘X’ on the top right corner? Or the one with the little, tiny “Cancel” link, hiding neat the bottom.\n\nBut it gets worse. Because some of these will dynamically center themselves... so, as you attempt to scroll around, to find the dismiss button, it will continually adjust itself, to stay in the center, and keep those dismiss controls properly hidden.\n
- #49 I had this awesome example, where National Geographic had the lightbox from hell, but...\n\nThey seem to have fixed it. \n\nOh well. \n\nI mean, YAY!\n
- #50 One mitigation strategy for popovers and lightboxes, at least in terms of advertising, is ... one of my least favorite bait-and-switch techniques. But, at least it’s not a lightbox.\n\nThe link redirects to an ad or video, and then has a x second timer that will take you back to the link you actually wanted. While generally, this is a rage item, it’s the lesser of evils.\n
- #51 We all know that navigation on your site is important. Once you have people there, you want to keep them.\n
- #52 Sorry guys, but...\n\nOn mobile, the size of the links/buttons make a huge difference in the usability of your web applicaiton. While those little ‘x’ close/delete buttons may seem like a good idea on the desktop, to maximize your available space for stuff like “text”, but missing the link can sometimes do... something completely different\n
- #53 But it isn’t just about the size of your links and buttons. You can actually leave the size alone, if it seems reasonable, and readable, but then you will need to adjust the spacing between your links and buttons.\n
- #54 Here is an example from one of my applications.\n\nWe made a sizing change (on the accordion headers), and we made padding and margin changes on the rest of the links\n\n
- #55 \nOf course, you can go and read the Apple Human Interface Guidelines (and you probably should anyway), but I’ve found that good, visual example is always superior to reading dry facts and figures.\n\n\n
- #56 PhoneFinger is a nice little Mac app that changes your mouse cursor into a full size finger, for use with the iPhone and iPad simulators. Reading Human Interface Guidelines is good, this is better. You will experience exactly the kinds of annoying missed link, wrong link clicked kinds of problems that your visitors are experiencing.\n
- #57 And now we come to one of my personal demons. Form entry on mobile.\n\nI could go on for hours, but I’m running out of time, so lets just concentrate on \n\nsignin, signup, profile editing.\n\nBelieve me, you will find MORE than enough rage-worthy problems, on just those 3.\n
- #58 Starting with signin ... most services these days let you use an email address as your account identifier. But how many of those services actually take advantage of the mobile convenience known as the custom keyboard?\n
- #59 Google fails here.\n\nFacebook wins!\n
- #60 Oh, sorry, Facebook, but you fail on the iPad...\n\nConsistency much?\n
- #61 That’s ok, Eventbrite failed too.\n\n
- #62 Twitter - Fail\n\nWordpress - Fail\n
- #63 Yahoo - FAIL\n\nMicrosoft Live - WIN!\n
- #64 Amazon - WIN!\n\nApple Store - FAIL?!?\n\nAnd, if you are going to say “use the app”, I’ll just have to mention that you can’t actually buy anything from the app, unless you’re in the US Apple Store.\n\nWTF?\n
- #65 The simple fix here, which is almost too embarrassing for words\n
- #66 And let’s move on to sign up.\n\nHere, I have a nice little anecdote, of attempting to sign up for a new service that everyone on Twitter was recommending a few weeks ago.\n
- #67 Username. No, I don’t actually want that auto-capitalized, thanks.\n\n
- #68 And autocompletion on this field doesn’t help me either, dammit.\n\n
- #69 Ok, fine, at least give me the email keyboard... no?\n\n
- #70 Are you kidding me? Autocomplete on my email? Grrrr.\n\n
- #71 I give up. You win.\n\n\n
- #72 I give up. You win.\n\nOr maybe I should say, you loose. Because I gave up, and iDrive lost a new customer.\n
- #73 Here is a fix for the autocomplete, although, I understand you may have to make it a form attribute, as well, for Firefox browsers\n\nAs for the password thing, it’s not really a mobile thing, but... don’t make arbitrary decisions about these restrictions.\n
- #74 Now a lot of the stuff you’ve seen is \n
- #75 \n
- #76 And here I enter in my homepage address with the custom keyboard for URL’s... \n\nOh, Twitter. FAIL again.\n
- #77 The simple fix here, which is almost too embarrassing for words\n
- #78 \n
- #79 Oh... I don’t think I have to demonstrate this AGAIN do I?\n
- #80 The simple fix here, which is almost too embarrassing for words\n
- #81 \n
- #82 \n
- #83 \n