App Quality Dashboard

Music Player

1.7 / 5

Chhi Score

This app is performing

Poor

Medium Risk

/5

High Risk

/5

Good 

/5

High Risk

/5

#

 

Category

Rank

  • Install time: Icon 7.67 Sec
  • Launch time: Icon 1.17 Sec
  • Application size: Icon 2.42 MB
  • Last tested on : 25/03/2017
  • Build ID
    :   v2.0.0
  • Chhi Score
    :   1.7
  • Change Rate
    :   +21.43 %

What to fix?

11 Risk(s) are due to Data Sent/Received in Network 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 20 CPU risks.

Potential risk in Network: Utilization has gone up by61.29% compared to build 1.1.8

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

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

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

Fixing Network risks could drastically improve Chhi Score. There are 11 Network risks.

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

20 tests need immediate attention. View performance graph.

App size increased by 39.88% See how to optimize.

The app's Memory score has improved by 25% compared to build 1.1.8! Good job!

The app's CPU score has improved by 6.25%

Consider re-merging the code from build 1.1.8, Network score was 3.1

Caching: Use LruCache for data caching to optimize memory usage

140 apps having similar CPU load have low Chhi Scores

Network utilization on Lenovo A6000 exceeded 1024 KB, you might want to consider bringing it down

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

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

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

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

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

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

Total Network data consumed was 6615.08KB in Lenovo A6000 , This indicates the app will take 10-15 seconds on 2G network and 8-9 seconds on 3G network to load! View details

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

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

Network utilization on Zenfone 2 Laser exceeded 1024 KB, you might want to consider bringing it down

App makes 6615.08 KB of network requests. Moving this to a background thread will improve load speed. View details

41.62 MB of App Dalvik utilized by activity com.ijoysoft.music.activity.MainActivity. View details

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

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

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

Screen Coverage

competition benchmark

This app is ranked #501 in Video Players & Editors

496
497
498
499
500
back-to-top