Mobile applications, like any product or service has its own lifecycle. The knowledge is primarily identify its weaknesses and best fit the needs of mobile users.According to Josh Clark, author of Tapworthy: Designing Great iPhone Apps, these mobile users do not open on average twenty times a small application, and only a third of installed apps are used after 30 days.
With the exception perhaps of daily use applications such as weather or RSS readers (although ...). Moreover, in this regard, we published some figures on the French mobile users in general and users in particular tablets.In short, the application life is generally short ...
According to that produced by computer graphics UXmatters, the life cycle of a mobile application involves five steps:
But what are these conditions? Poof, poof, here is a summary of good advice given by UXmatters.
The application window
An application is accepted on the App Store do not ensure that it is 1) easily found by mobile users and 2) they will want to install.The App Store is a store of a very particular format because it allows mobile users not to touch and experience the product, as you would in physical outlets (ok, maybe not to the bakery).To make his choice, the user is therefore based on four types of information: the price of the application, description, screenshots and notes of other users.Our tip: highlight and describe precisely what is going to attract the interest of mobinaute and answer questions.
The opening and discovery
Open an application you just installed, it's a bit like when you tear the wrapping paper of a package that is known about what's in it: if you're disappointed, we pass to something else.
This is THE moment the mobinaute acquainted with your application and its interface, it will measure very quickly.
The user will then try to test the basic functionality of your application. For example, if I want all my recipes on my iPhone, I'll soon find out how to add ingredients and how to write a recipe. If I put more than two minutes (and again) to find how to reach my goal, or worse, if I realize that this application is just a collection of recipes published by others, I will go my way and I will try a another application.
Our tip: anticipate features that mobile users will find the first and make them easily accessible, at risk of being thrown in the trash quick well done.
The deepening and updating
If your application passes the third step, you are near the goal! Because if I found, downloaded, opened and tested (and approved) the application, it's a safe bet that I will try other features to see what it was in the belly.
If I take the example of the cookbook, after testing the basic functionality, I'll look how to share my recipes (by mail, social networks, etc..), How to print, how to add pictures to that they are all pretty, how to add custom tags for easy retrieval, etc.. etc..
And if I am convinced I will keep this application on my iPhone and even (drum roll) the update. This last step is essential because, even if your application has spent the previous four without mishap, we must continue to adapt (to new OS for example) and develop to enrich the user experience (for example, follow the changes in usage on the social web and propose sharing features).
Then, the loop is not fastened, O cruel world of mobile applications: you must continue to prove yourself as you return to square one for new users, not to mention time and again to raise the interest of those who have already installed on their mobile.
Our tip: bet on an ergonomic interface, the study of the user experience, and of course about webdesign ... you find elsewhere in the thread of each of these phases, the setting to showcase update.
This post is heavily inspired by a recent article on UXmatters called The Lifecycle of a Mobile App, a User's Perspective.
With the exception perhaps of daily use applications such as weather or RSS readers (although ...). Moreover, in this regard, we published some figures on the French mobile users in general and users in particular tablets.In short, the application life is generally short ...
According to that produced by computer graphics UXmatters, the life cycle of a mobile application involves five steps:
- The setting window of the application on the App Store;
- The opening of the application for the (entire) first time (always first time);
- The discovery and use of basic features;
- Deepening and use more advanced features;
- Updating.At each step;
The application in question can be suppressed without mercy by the user if it does not satisfy the conditions (here represented by small red circle that reads "delete app" - yes, I have good eyes, thank you).
But what are these conditions? Poof, poof, here is a summary of good advice given by UXmatters.
The application window
An application is accepted on the App Store do not ensure that it is 1) easily found by mobile users and 2) they will want to install.The App Store is a store of a very particular format because it allows mobile users not to touch and experience the product, as you would in physical outlets (ok, maybe not to the bakery).To make his choice, the user is therefore based on four types of information: the price of the application, description, screenshots and notes of other users.Our tip: highlight and describe precisely what is going to attract the interest of mobinaute and answer questions.
The opening and discovery
Open an application you just installed, it's a bit like when you tear the wrapping paper of a package that is known about what's in it: if you're disappointed, we pass to something else.
This is THE moment the mobinaute acquainted with your application and its interface, it will measure very quickly.
The user will then try to test the basic functionality of your application. For example, if I want all my recipes on my iPhone, I'll soon find out how to add ingredients and how to write a recipe. If I put more than two minutes (and again) to find how to reach my goal, or worse, if I realize that this application is just a collection of recipes published by others, I will go my way and I will try a another application.
Our tip: anticipate features that mobile users will find the first and make them easily accessible, at risk of being thrown in the trash quick well done.
The deepening and updating
If your application passes the third step, you are near the goal! Because if I found, downloaded, opened and tested (and approved) the application, it's a safe bet that I will try other features to see what it was in the belly.
If I take the example of the cookbook, after testing the basic functionality, I'll look how to share my recipes (by mail, social networks, etc..), How to print, how to add pictures to that they are all pretty, how to add custom tags for easy retrieval, etc.. etc..
And if I am convinced I will keep this application on my iPhone and even (drum roll) the update. This last step is essential because, even if your application has spent the previous four without mishap, we must continue to adapt (to new OS for example) and develop to enrich the user experience (for example, follow the changes in usage on the social web and propose sharing features).
Then, the loop is not fastened, O cruel world of mobile applications: you must continue to prove yourself as you return to square one for new users, not to mention time and again to raise the interest of those who have already installed on their mobile.
Our tip: bet on an ergonomic interface, the study of the user experience, and of course about webdesign ... you find elsewhere in the thread of each of these phases, the setting to showcase update.
This post is heavily inspired by a recent article on UXmatters called The Lifecycle of a Mobile App, a User's Perspective.
