Attending Mobile Camp in Boston this past Saturday I listened to a presentation by a developer that indicated that some mobile apps may be victimized by customer issues more than then apps actual functionality. It turns out that often customers rate apps negatively for reasons that have very little to do with the app. It struck me that if developers took more time to learn what elements of their apps will drive excitement and satisfaction then they may be able to elicit more positive reviews (the 5 star nirvana necessary to vault to the top of the ratings chart and garner more downloads).
With applications, just like software, some features are a given, such as ease of installation, compatibility with my OS (or OS flavor in the case of the Android), and of course how streamlined. In the past a “front-end” to a company’s mobile-enabled website might have been acceptable, now that is viewed as archaic and outdated. Customers seek speed, easy interaction and security (features defined as Execution). The Kano Model proposes there are several attributes that entice customers and will allow you to keep them:
Performance features are a function of Threshold or Required features
Required or Threshold features: This is what is expected. If you have a banking app you would expect to be able to access your accounts and at the very least verify balances and transactions and transfer funds between accounts at the same bank.
Excitement features could be the ability to transfer funds between two different banks, wire funds to a cousin via Western Union, etc. These are the unexpected features that a customer will rave over when reviewing an app.
You may have guessed – Excitement features will become with time required features. So give more thought as to how you can keep customers downloading your apps via going the extra leg without giving it all away (stay in the upper write quadrant).

