by Roberta J. Witty | August 8, 2013 | Comments Off on What’s a Happy App?
After researching BCM for so long, it’s making me think of the exact opposite: what does it mean to be safe, free, happy. It’s the same reaction as when you stare at something yellow for a minute: when you look away, you see purple. Same thing for red and green. There is always a flip side to every thing. So, I’ve started thinking about what it means to be happy in an IT environment, an IT company – the whole IT experience. I’m calling it “Bliss Management.”
So I’m starting with: What’s a happy app? I had an experience of a ‘not so happy’ app the other day when ordering an item on the Internet via my mobile device. When you are requested to enter the expiration date for your credit card information, why does it have to start at January, or worse 01? Why not start the drop down menu in the middle of the year – June or July? It is much more efficient as you only have to scroll through 6 or fewer entries rather than 11 if you are a December expiration. Also, when the app requests you to enter your email address or a number, why does it not provide you the right keyboard layout with numbers and the @ sign?
Is there some technical reason why it doesn’t happen? Or are programmers just that lazy? Or do they just not think about the human experience? Both of these minor changes can make the end user happy. Isn’t that what online retailers want?
Read Complimentary Relevant Research
Predicts 2017: Artificial Intelligence
Artificial intelligence is changing the way in which organizations innovate and communicate their processes, products and services. Practical...
View Relevant Webinars
How to Live Without Mobile Device Management
This webinar addresses the growing trend of users refusing to have enterprise management of their mobile devices due to privacy concerns....
Comments or opinions expressed on this blog are those of the individual contributors only, and do not necessarily represent the views of Gartner, Inc. or its management. Readers may copy and redistribute blog postings on other blogs, or otherwise for private, non-commercial or journalistic purposes, with attribution to Gartner. This content may not be used for any other purposes in any other formats or media. The content on this blog is provided on an "as-is" basis. Gartner shall not be liable for any damages whatsoever arising out of the content or use of this blog.