App Quality Dashboard


2.3 / 5

Chhi Score

This app is performing


Medium Risk


Medium Risk




Medium Risk






  • Install time: Icon 13.50 Sec
  • Launch time: Icon 2.24 Sec
  • Application size: Icon 3.33 MB
  • Last tested on : 26/03/2017
  • Build ID
    :   v1.3.2
  • Chhi Score
    :   2.3
  • Change Rate
    :   +35.29 %

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.

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

6 Risk(s) are due to App PSS in Memory exceeding the threshold. See how to optimize memory and remove 6 High Risk(s).

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

Build v1.3.1 did better in Memory . Spikes in Memory contributed to score drop by 23.08%

7 tests need immediate attention. View performance graph.

Consider re-merging the code from build v1.3.1, Memory score was 2.6

The app's Network score has improved by 25% compared to build v1.3.1! Good job!

The app's memory score is 2.0 due to high memory utilization. Needs to be fixed as priority.

1 Risk(s) are due to CPU Load in CPU exceeding the threshold.

The app's CPU score has improved by 22.22% compared to build v1.3.1! Good job!

App size increased by 17.67% See how to optimize.

Make sure your App's PSS isn't too high. Freeing objects that aren't needed would reduce chances of getting unexpectedly killed by Android system.

2 Risk(s) are due to App Total in Memory exceeding the threshold.

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

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

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

Caching: Use LruCache for data caching to optimize memory usage

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.

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

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

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

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.

45.91 MB of App Dalvik utilized by activity View details

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

Your average App Dalvik usage surged by 14.25%, Your memory score is 2.0

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

Well done, Network consumption has come down by 32.61 % compared to build v1.3.1

Screen coverage

competition benchmark

This app is ranked #599 in Music & Audio