22 February 2023
Close
11 February 2020
4 MIN READ 
BY
Pradeep K
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 checklist prior to your Mobile Application Publishing to enhance the quality of your App .
Ensure that analytics have been installed before pushing the App into production. We need to ensure that analytics are collected in terms of active time, number of times a user opens an app, most opened features by users, and events. We should implement one of the analytic tools, such as Power BI Analytics, Firebase Analytics, or Amazon Mobile Analytics.
Crashlytics includes the messages and locking system of an App. They are traced and displayed in the dashboard. We can also use Crashlytics to trace misbehaving apps.
Use Proguard to refactor 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.
We must reduce the APK size as much as possible. Mobile apps in the Playstore usually range in size from 10 to 20 MB.The maximum permitted size by playstore is 40MB for mobile Apps and 70 MB for games. The Android Studio analyze APK tool can be used to analyze the size of apps and remove unwanted resource files and PNGs.
We should carry out proper testing for mobile apps before releasing them to the market, as the adoption rate of upgraded versions is very low. 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.
Always ensure to turn off logging and debugging, as some developers usually forget to turn it off. If the logging is not turned off before pushing, there is a high chance that the system will be crashed or hacked because of the information available in the logs.
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.
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.
We should model the performance of the app by focusing on the section of users who are installing the app. Analytics helps in analyzing the most needed features by users, such as low memory, mostly downloaded versions, etc. We can develop a compatible app that meets user needs with the help of this information.
To ensure a smooth user experience, we need to ensure that the frames per second (FPS) of the UI is sufficient, especially in gaming apps. We should carefully analyze the number of frames used in each activity, especially when loading recyclers and other complex views.
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. We should code in a way that is suitable for localization, even if localization is not implemented in the initial stage. e should properly code error messages, communication messages, etc. in the string.xml file. We should take special care in apps that use RTL (right-to-left) languages, such as 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.
10 December 2021
