With every passing day the number of mobile applications developed and included in different mobile application stores like the Google play-store, Microsoft store, and Apple store is increasing at a rapid pace. The developers of these mobile applications do not follow a pre-defined or standardized procedures while writing and designing the application.
What should be the different parameters to measure the performance and quality of a mobile application?
Although latest mobile devices are quite good with resources but the limitation of resources to run applications is still a problem. The applications should be designed with following perspectives in mind.
1- Make sure that any resource like memory or process that is not being used anymore should be release. It can turn up to be bottleneck on mobile device soon compared to normal computing devices like computers.
2- Quality testing is very important. Any process or feature that uses memory should be watched to see if it actually has a requirement for increased memory as it runs. It should be tested with this application running alone or with other apps running in background and see if there is any difference in frequency of memory increasing. Decision has to be made if it actually needs to store all that information or it can keep a snapshot and load details when required or demanded.
3- Battery consumption is a major problem in apps. They can be wonderful but useless if they eat battery. Usually it is done by keeping those threads/processes alive when it is not really required or the interval between them is unnecessarily shorter making it heavy for battery. Also it can be seen easily if the application is tested at least for 24 hours - that should tell the pattern of battery consumption. The functions should be decomposed to see what exactly is causing that and then algorithm should be analysed if it can be optimised.
Hope that helps.
According to these guys, the leading performance indicators are these:
http://apigee.com/about/pressrelease/apigee-survey-users-reveal-top-frustrations-lead-bad-mobile-app-reviews
Freezes – 76%
Crashes – 71%
Slow responsiveness – 59%
Heavy battery usage – 55%
Too many ads – 53%
According to the Common Wisdom, an app has to provide a response within 3 seconds - no matter how it achieves this speed (typically 3 seconds over a congested mobile network is not enough for a response but the app should provide _something_ in that timeframe).
You should not forget the quality of user experiences (QoE). This is a subjective measure based on users perception of quality and their feelings while using the application.
You can find questionnaires that help you to measure this value. E.g. the AttrakDiff questionnaire, which works also for multimodal systems like current smartphones or tablets. It includes 28 pairs of attributes that help you to measure users perceived quality.
Measuring the QoE helps you to understand the quality perception of final users, who are definitely who will use and/or buy your app.
Hope that helps and provides a different perspective por apps quality measurement.
- Badges
- Science topic
- Similar topics
- Correction