A lot of confusion arises when your App is in the budding stage. The acceptance or rejection of
an App depends on several factors which are a result of mobile application testing. Being a
software testing service company, Testvox recommends to go with the following checklists on
how to improve your mobile App quality.
Before pushing into production ensure if analytics have been installed or not. Analytics to be
ensured are in terms of active time, Number of times a user opens an App, mostly opened
features by users and events. Any one of the analytic tools such as power based analytics,
Firebase analytics or Amazon mobile analytics should be implemented.
Crashlytics includes the messages and locking system of an App. Crashlytics are traced and
displayed in the dashboard. Crashlytics can be also used to trace out misbehaving Apps.
Proguard is used for refactoring the App code before loading to prevent reverse engineering.
Proguard is only mandatory for production code. Codes in the production stage should be
thoroughly verified as there are chances for misbehaving of App. This happens because
sometimes it deletes unwanted files and codes.
4. Shrink APK size:
The APK size must be reduced maximum. Usually, the size for mobile Apps in playstore is
found to be between 10 to 20 MB. The maximum permitted size by playstore is 40MB for mobile
Apps and 70 MB for games. Size of Apps can be analyzed with the help of analyze APK tool
provided by the android studio to remove unwanted resource files and PNGs.
Proper testing for mobile apps should be carried out properly before the market release, as the
adoption rate of upgraded version among customers is very less. So ensure unit testing and
instrumented UI testing in development stage itself. Tools for UI testing of mobile apps is
provided by android studio which auto generates test cases to ensure correctness of UI.
6. Turn off logging and Debugging:
Always ensure to turn off logging and debugging, as some developers usually forget to turn it
off. If pushed without turning off the logging, there are high chances of the system being
crashed/hacked because of information available in logs.
7. Be ready with 'What's new" content:
One of the common mistakes that developers make is with the content of what's new which
goes like "Bug fixes and performance improved". This pulls customers backward from installing
the Apps. So be sure with the contents in What's new by making it more descriptive and catchy.
8. Latest screenshots:
Put forth in front of customers what they are going to see once they install the App. Try to show
the screenshots regarding the core functionality of the App instead of usual Login and sign Up
pages along with tiny descriptions. For example, consider Gmail where the screenshots should
dispense "compose" section rather than login.
9. Application performance:
Performance of the App should be modeled focussing on the section of users installing the
particular App. Analytics helps in analyzing the most needed features by users, such as low
memory, mostly downloaded versions, etc. With the help of this information, a compatible App
with users need can be developed.
10.Frames per second:
To solve the issues in the views especially in gaming Apps, frames per second should be
ensured for particular UI. The number of frames used in each activity should be carefully
analyzed like while loading recycler and other complex views.
11. Cpu and Memory usage and Network Traffic
It is a good practice to keep a memory limit for Apps and release the memory as soon as this
limit exceed depending upon the nature of the App. This will contribute to the reduction in
memory utilization by the App by releasing the data it stores in the cache.
Large utilization of data by Apps can lead to uninstallation. To ensure minimum data usage by
App by reducing the API requests to its maximum thus increasing its offline features. Paging
library can be helpful in loading large data into small chunks.
Localization is the feature that helps to extend an App's each to a large section of users. Even if
not implemented in the initial stage it will be helpful if the coding is done so as to suit localization
later. So error messages, communication messages, etc should be properly coded in string. xml
file. Special care should be adopted in the Apps that use RTL(Languages like Arabic).
Ensure the working of UI after the implementation of localization to check misbehaving of Apps.
Give pop up messages in App without annoying the customers to get rating and review as it is
very important for App in its budding stage.