App Quality Dashboard


1.3 / 5

Chhi Score

This app is performing


Medium Risk


High Risk










  • Install time: Icon 28.47 Sec
  • Launch time: Icon 2.36 Sec
  • Application size: Icon 12.28 MB
  • Last tested on : 10/03/2017
  • Build ID
    :   v2.0.4-release
  • Chhi Score
    :   1.3
  • Change Rate
    :   0%

What to fix?

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

Your App CPU is now in a High Risk Zone. With a small investment into your testing you can improve your app quality better. Get more test coverage

Potential risk in CPU: Utilization has gone up by 6.67% compared to build v2.0.3-release

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.

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

Build v2.0.3-release did better in Memory . Spikes in Memory contributed to score drop by 5%

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

19 tests need immediate attention. View performance graph.

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

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

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

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

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

5 apps having similar CPU load have low Chhi Scores

86.61 MB of App Dalvik utilized by activity View details

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

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

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

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.

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

Your average App Dalvik usage surged by 0.98%, Your memory score is 1.9

Caching: Use LruCache for data caching to optimize memory usage

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

Well done, Network consumption has come down by 40.2 % compared to build v2.0.3-release

The app's Network score has improved by 13.16% compared to build v2.0.3-release! Good job!

Screen Coverage

competition benchmark

This app is ranked #17 in Events