2.2 / 5

Chhi Score

This app is performing


Medium Risk


Medium Risk










  • Install time: Icon 35.36 Sec
  • Launch time: Icon 1.06 Sec
  • Application size: Icon 33.09 MB
  • Last tested on : 16/05/2017
  • Build ID
    :   v2017.05.08-release
  • Chhi Score
    :   2.2
  • Change Rate
    :   -21.43 %

What to fix?

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

Build v2017.04.19-release did better in Memory . Spikes in Memory contributed to score drop by 30.77%

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

Build v2017.04.19-release did better in CPU . Spikes in CPU contributed to score drop by 25%

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.

App launch time went up by 19.1% initlizate network calls after few seconds of loading the resources. View details

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

13 tests need immediate attention. View performance graph.

Consider re-merging the code from build v2017.04.19-release, CPU score was 2.4

Consider re-merging the code from build v2017.04.19-release, Memory score was 2.6

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

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

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

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

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

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

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

Caching: Use LruCache for data caching to optimize memory usage

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

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

41.87 MB of App Dalvik utilized by activity View details

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.

competition benchmark

This app is ranked #641 in Music & Audio