I love updates! Or the app story the Nielsen Norman Group doesn't tell

Every product is a design theory embodied. Designers and developers make something based on their theory about what is good and fun and useful and enjoyable, ideally for a particular audience. The theory is tested when people begin to use the product and we discover how closely our assumptions and people’s reality line up.

In the spirit of theory testing, the Nielsen Norman Group recently posted findings from their iPad Usability study where they reported on the usability of 35 iPad apps and reported that the experiment to date is pretty much a failure from a usability perspective:

“iPad apps are inconsistent and have low feature discoverability, with frequent user errors due to accidental gestures. An overly strong print metaphor and weird interaction styles cause further usability problems.”

Jakob Nielsen’s Alertbox, May 10, 2010

 

For most of the history of software development, that would be the end of the experiment, in this case, a demonstration of the application creators significant failures to align the designed applications with the user’s needs or expectations.

 

But wait! There’s an update coming! and that is the magic of iPad apps right now. It is not in their perfection or consistency or even their usability. Yeah, iPad apps sorta suck, but that is also their charm. They are a reflection of the American dream, where even an app of humble, quirky beginnings can someday be great.

As a user, when I think of the apps on my iPad, I imagine somewhere a group of hardy, imaginative and playful people trying to make sense of this technology and invent a bit of the future for me. They are not going it alone though. I’m there too. I am in their proverbial garage, giving them my wish list, sharing my complaints, cheering them along, trusting that the next update they come out with is going to be totally awesome.

I am a micro-patron of the application creator, having invested my $2.99 in both the app as it is now and what I hope it will be in the future. The cost is usually low, and I invest in many applications, hoping a few will go big—meaning they will become an enjoyable part of my life. It’s a bit of a stock market or lottery, in that it’s about dreams and imagination and uncertain future gains. But unlike those games of chance, I have a voice, a direct channel to the people releasing the next update. We are a tiny bit like co-workers, they build, I test and report, and then they build again. I believe that the application and the makers are on a trajectory towards mastery, with my help.

Example: Popplet user feedback on application page. Note feature lists and a sense of connection between the users and the makers. Click image to see larger text.

Given this new framework of shared co-creation and evolution, a question you might be asking yourself now is, so when should I launch my app? Can I launch “early”?

Sure, you can launch early but here are six things to keep in mind:

1. There is not such thing as launch and leave

Don’t plan or resource your project thinking that the design or development effort is going down after you launch. If things go well, you will have a whole lot more to work on.

2. Do at least one thing really well.

A favorite story about product development is that we want to make cupcakes and then cakes and then wedding cakes, instead of cake and then filling and then icing. People like small yummy cupcakes. A big ole cake with no icing or filling, not too charming or sell-able. Think about your product roadmap as a series of delicious releases.

3. Baseline: Don’t take down the system

If your app crashes, do not launch. Really, that’s just lame.

4. Don’t over promise and under deliver

Be confident about what your app does do. Promising things it doesn’t quite do is insecure and we’ll find out real quick.

5. This game is all about transparency, humility, compassion, and communication.

People aren’t buying apps, we are investing in experiences that we are trusting you to create. Honor your creation process, share your challenges and triumphs and we will appreciate your work.

Example: Popplet shares it’s development constraints and aspirations for people to have good experiences with the app. Click image to see larger text.

6. We are patient if you are quick

Essentially, we can’t wait for the next update!

 

 

 

Add to the conversation.

Commenting is not available in this channel entry.