App Quality Dashboard


1.0 / 5

Chhi Score

This app is performing


Medium Risk


High Risk




Medium Risk






  • Install time: Icon 18.37 Sec
  • Launch time: Icon 2.48 Sec
  • Application size: Icon 9.07 MB
  • Last tested on : 27/04/2017
  • Build ID
    :   v3.0.6
  • Chhi Score
    :   1.0
  • Change Rate
    :   +11.11 %

What to fix?

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

Build v3.0.5 did better in Network . Spikes in Network contributed to score drop by 26.32%

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

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 25 CPU risks.

Consider re-merging the code from build v3.0.5, Network score was 3.8

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

25 tests need immediate attention. View performance graph.

The app's Memory score has improved by 3.57% compared to build v3.0.5! Good job!

Utilization of CPU is close to the threshold.

Utilization of Network is close to the threshold.

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

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.

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

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

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

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

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

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

78.85 MB of App Dalvik utilized by activity View details

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

Caching: Use LruCache for data caching to optimize memory usage

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

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

435 apps having similar CPU load have low Chhi Scores

Screen Coverage

competition benchmark

This app is ranked #1317 in News & Magazines