App Quality Dashboard


3.8 / 5

Chhi Score

This app is performing


Medium Risk


Medium Risk










  • Install time: Icon 11.53 Sec
  • Launch time: Icon 2.08 Sec
  • Application size: Icon 5.71 MB
  • Last tested on : 03/05/2017
  • Build ID
    :   v23.2
  • Chhi Score
    :   3.8
  • Change Rate
    :   -5 %

What to fix?

Test more often so that you don't break the CPU handling further in your next builds. CPU Score is in danger zone. Heavy battery consumption expected.

15 Risk(s) are due to Threads in CPU exceeding the threshold.

Fixing CPU risks could drastically improve Chhi Score. There are 15 CPU risks.

Build v23.1 did better in CPU . Spikes in CPU contributed to score drop by 9.52%

Build v23.1 did better in Memory . Spikes in Memory contributed to score drop by 5.26%

The app has a high performance risk for the phone manufacturer(s) Samsung, Panasonic, Lenovo, Motorola, LYF, Micromax. Check coverage report for more details.

16 tests need immediate attention. View performance graph.

Fix Oncreate() if the launch time is exceeding more than 3.2 secs. Try deflating views and layouts to optimize.

37.30 MB of App Dalvik utilized by activity com.nll.acr.activity.MainActivity. View details

Upload APKs with and without 3rd Party SDKs to monitor and optimize the impact of app performance

Fix & Optimize launch time using Flatbuffers for storage and rendering performance.

There is high probability of identifying risks running the apps with conditions

Coverage: Android version coverage for reports will range between 5.1.1 to 7.1.2

Printing logs on callbacks would make debugging easy for tests run in our platform

Below 10 MB approach would increase app installs in crowded markets such as India, China and Russia!

Do not initialize objects that aren't necessary during launch times. Moving to singleton pattern helps

Your average App Dalvik usage surged by 9.31%, Your memory score is 3.6

Avoid wake-locks in background, using Batch and schedulers APIs such as GCM, Job schedulers could reduce wake-locks

Optimize the app to render elements at 60 FPS for buttery smooth experience.

Caching: Use LruCache for data caching to optimize memory usage

Testability: Providing login / sign-up details could very well improve depth of bot clicks

Follow simple UI hierarchy by reducing nested layouts to Relative layouts.

Well done, Network consumption has come down by 22.69 % compared to build v23.1

The app's Network score has improved by 2.27% compared to build v23.1! Good job!

competition benchmark

This app is ranked #484 in Productivity