App Quality Dashboard

edjing Mix

2.4 / 5

Chhi Score

This app is performing


Medium Risk


Medium Risk










  • Install time: Icon 40.80 Sec
  • Launch time: Icon 3.29 Sec
  • Application size: Icon 38.45 MB
  • Last tested on : 24/04/2017
  • Build ID
    :   v6.2.5
  • Chhi Score
    :   2.4
  • Change Rate
    :   +118.18 %

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.

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

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

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

The app's Memory score has improved by 46.67% compared to build v6.2.3! Good job!

15 tests need immediate attention. View performance graph.

Utilization of CPU is close to the threshold.

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

The app's CPU score has improved by 19.05% compared to build v6.2.3! Good job!

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

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

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

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

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

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

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

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

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

Caching: Use LruCache for data caching to optimize memory usage

43.95 MB of App Dalvik utilized by activity com.facebook.FacebookActivity. View details

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

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

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

Well done, Network consumption has come down by 52.14 % compared to build v6.2.3

The app's Network score has improved by 9.52% compared to build v6.2.3! Good job!

competition benchmark

This app is ranked #569 in Music & Audio