Cath's recent post about Mappiness , and my response, prompted me to think about habits. How we form them, how we break them and how, as designers of utilities and services, we can build our apps to encourage habits to form in users.
After all, don't we want the things we build to be adopted and used regularly by thousands (millions!) of people?
But we all know that is difficult. Apps that look great on first glance, are downloaded with a sense of eager anticipation but are abandoned in the fetid wasteland that is three screens into your iPhone a few weeks later are all too common.
Why is this?
This wouldn't be a blog post without a bit of personal opinion so here's what I think. And before we go on I just want to clarify that I'm not talking about games, RSS readers or weather apps. But those other apps that record data and information over time and require input form the user on a regular basis.
I feel that for an app to really succeed it needs to become embedded in the user's daily behaviour. The app that Cath wrote about, Mappiness, uses push notifications to get the user's attention and prompt them to interact or do 'a thing'. In this case the 'thing' is to track mood against location, and other variables, each day.
But the way it goes about it is a bit blunt. A clumsy mechanism which says "Oi, over here, look at me!" As Cath points out, the notifications usually come at the most inappropriate time and increasingly get ignored as the novelty of the app wears thin.
Once upon a time I rode a bike competitively. I read an article back then about the psychology of training and how, if we really want to form a habit, we need to do something 21 times. So, once a day for 3 weeks, once a week for 5 months… It went on to discuss ways in which you could help form these habits by integrating them into our daily routine. If you want to take a multi vitamin every day you put the bottle next to your cereal packet or bowl in the cupboard.
If we can apply that same thinking to the apps we develop then perhaps we can abandon our reliance on crude push notifications to cajole our users into participating.
One such app does this perfectly, for me, is Cyclemeter. It tracks mileage, average speed, maximum speed and route while I'm out cycling. All I need to do is press start before I set off and stop when I get back home. I'm already putting the phone in my pocket before I set off. I now have an automatic reaction to set the app going at that point. The return? A load of data about my ride. It doesn't disrupt my workout or any calls I may receive. It just does its thing in a completely frictionless way.
So what are the mechanisms we can employ to create habits in users without relying on interruption to attract participation?
-
Design your app or service so that it integrates into something the user already does in their daily routine. Piggybacking off already engrained habits.
-
Try to make the point of interaction as quick as possible. How can I gather as much information without asking the user to do too much? Think one button press.
-
How can you give the sense to the user that they are getting more back than they put in? What's the value exchange?
-
Do ONE thing and do it well. It's been mentioned a thousand times and there's a reason for that.
So, any other thoughts on how to form user habits to encourage participation? After all, Tim's suggestion of 'tech embedded inside our bodies' is a little way off.