1. When it comes to apps, it's a user's market.
If an app doesn't give a user what they want, they'll look elsewhere for one that does. Or, from personal experience, they won't bother at all. I tried using my bank's mobile app some time ago and frustrated by the experience of having to continually re-input and re-select data from one screen to the next, I reverted to their website interface. Entering text on a mobile is not an exact science, particularly when you've got clumsy great digits like I have. The interface and requirement for user interaction should be simple and intuitive.
2. Successful apps give users "mobile moments".

Another example of this was when I tried to book tickets via my mobile. The pop-up keyboard completely obscured the box I was trying to fill out, so I was left blindly trying to input my credit card number. All the while, the number of available tickets was shrinking fast. I got there in the end but my mobile moment in using that app was one of frustration and just maybe a little bit shouty.
On the other hand, consider something like National Rail's app, which is tailored beautifully for the smaller screen. Data can be input simply, responses are delivered in a quick, fun and friendly way and the experience of discovering my train has just been cancelled is improved considerably.
3. Mobile development is maturing, with both investment and use still subject to experimentation.
With over 1.5 billion smartphones in operation, enterprises know that if they want to reach customers, they need to have an app. It's important to invest the time and money required to develop an app which engages the user, delivers what they want and helps them to do whatever it is the app helps them do, better. But of course they don't always get it right first time. Few rarely do. What matters though, is giving the user a worthwhile experience from the first iteration. It doesn't have to offer everything the enterprise aspires to do via its app, but it must at least perform a core set of functions and do it well.

But every iteration of the app has delivered what was promised. It works, it manages the watch effectively and it's a useful front-end to the bewildering variety of watchfaces and apps that the watch can run. And it did all of those things from day one.
![]() |
Pepsi's Amp Up app |
Pepsi's Amp Up Before you Score app, released in the distant past that is now 2009, was a game aimed at men designed to help them pick up one of 24 in-game female stereotypes.
I know, right? Needless to say there was an entirely justified outcry from consumers and media, alike, and the app was quietly pulled. Read The Guardian's article on that whole sorry affair.
5. Understand your cost drivers and how to manage them
A comprehensive understanding of the cost drivers behind your app can mean the difference between saving up to 10% on development costs or doubling them. How does the app fit into the enterprise's overall strategy; what does the enterprise hope to gain from the app, how will it simplify customer or employee interactions, what is its planned impact on productivity, what resources are available
It all comes down to the question of why the app is being created and how it fits into your business model. And when bearing those elements in mind, the prime concern is how all of this makes the life of your user or your employee just that little bit better.
A side effect of the mobile, always-on experience is that our attention spans have shrunk. The app user needs to be able to get what they want quickly and with no fuss. Therefore, an effective app must balance form against function. Complex data and processing must be represented in a highly simplistic, intuitive way. That's a challenge, but it's one the enterprise must face up to. A bad experience on the part of the user means they will be reluctant to go back for a second try.