Pull-to-refresh is one of the most popular gestures in mobile applications right now. It’s easy to use, natural and so intuitive that it is hard to imagine refreshing a page without it. In 2010, Loren Brichter created Tweetie, one of numerous Twitter applications. Diving into the pool of similar applications, you won’t see much difference among them; but Loren’s Tweetie stood out then.
It was one simple animation that changed the game — pull-to-refresh, an absolute innovation for the time. No wonder Twitter didn’t hesitate to buy Tweetie and hire Loren Brichter. Wise choice! As time went on, more and more developers integrated this gesture into their applications, and finally, Apple itself brought pull-to-refresh to its system application Mail, to the joy of people who value usability.
Brainstorming is notorious for being unstructured and often unactionable. People get in a room with some Post-its and whiteboards and expect the great ideas to happen. The problem is, even if there are great ideas in the room, there is often no clear-cut way to decide on what ideas to take action on.
Building a new service for a Fortune 500 company using applied user story mapping. That’s me facing the camera.
I once worked with a digital agency that didn’t know how to hold a kickoff meeting. And they didn’t even know that they didn’t know. Weeks into every project, they’d simply find themselves frustrated over how they’d ended up in a position of following rather than leading.
They would fight to get their good ideas out the door but end up on defense all the time when their clients came back screaming with arguments based on whim and vapor.
The internal systems of many organizations have shocking user interfaces. This costs companies in productivity, training and even the customer experience.
Fortunately, we can fix this. “How come I can download an app on my phone and instantly know how to use it, yet need training to use our content management system? Shouldn’t our system be intuitive?”
This was just one of the comments I heard in a recent stakeholder interview.
You probably hear about it every week, if not every day: a spiteful or ragged relationship has ended badly. There are bitter arguments, custody battles, legal entanglements, lives and homes broken in the wake of moral incompatibility, poor choices, and a lack of sober discrimination.
It’s the predictable result of kids getting married too young or impassioned people who barely know each other rushing into marriage. The tale is often similar with designers and their clients after a rushed, ill-considered marriage.
Steve Jobs stated once that the “design is not just what it looks like and feels like. Design is how it works.” While this statement has proven to be crucial over thousands of years, one shouldn’t misinterpret it by emphasizing the functionality despite the design. When it comes to product design, the significance of aesthetics of a given device, the way its design looks and feels, determines the choice of the customer once the functionalities of multiple devices are more or less similar.