App Quality Dashboard

Music Player

3.2 / 5

Chhi Score

This app is performing

Average

Memory

Medium Risk

/5

CPU

Medium Risk

/5

crash

Good 

/5

network

Good

/5

Competition

#

 

Category

Rank

  • Install time: Icon 6.60 Sec
  • Launch time: Icon 0.97 Sec
  • Application size: Icon 2.26 MB
  • Last tested on : 08/03/2017
  • Build ID
    :   v1.2.3
  • Chhi Score
    :   3.2
  • Change Rate
    :   +166.67 %

Insights (25)

What to fix?

7 Risk(s) are due to Threads in CPU exceeding the threshold.
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.
The app's CPU score has improved by 57.14% compared to build v1.2.2! Good job!
Utilization of CPU is close to the threshold.
The app's Memory score has improved by 87.5% compared to build v1.2.2! Good job!
The app has a high performance risk for the phone manufacturer(s) YU, Asus, Panasonic, LYF. Check coverage report for more details.
App size increased by 46.75% See how to optimize.
8 tests need immediate attention. View performance graph.
Printing logs on callbacks would make debugging easy for tests run in our platform
Below 10 MB approach would increase app installs in crowded markets such as India, China and Russia!
30.19 MB of App Dalvik utilized by activity com.ijoysoft.music.activity.MainActivity. View details
Optimize the app to render elements at 60 FPS for buttery smooth experience.
Avoid wake-locks in background, using Batch and schedulers APIs such as GCM, Job schedulers could reduce wake-locks
Follow simple UI hierarchy by reducing nested layouts to Relative layouts.
Testability: Providing login / sign-up details could very well improve depth of bot clicks
Caching: Use LruCache for data caching to optimize memory usage
There is high probability of identifying risks running the apps with conditions
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.
Upload APKs with and without 3rd Party SDKs to monitor and optimize the impact of app performance
Do not initialize objects that aren't necessary during launch times. Moving to singleton pattern helps
Coverage: Android version coverage for reports will range between 5.1.1 to 7.1.2
The app's Network score has improved by 213.33% compared to build v1.2.2! Good job!
Well done, Network consumption has come down by 91.97 % compared to build v1.2.2
Unlock more fixes

Screen Coverage

competition benchmark

This app is ranked #302 in Video Players & Editors

297
298
299
300
301
back-to-top