App Quality Dashboard

Zee Music Player

1.0 / 5

Chhi Score

This app is performing

Poor

High Risk

/5

Medium Risk

/5

Good 

/5

Medium Risk

/5

#

 

Category

Rank

  • Install time: 11.72 Sec
  • Launch time: 4.67 Sec
  • Application size : 4.05 MB
  • Last tested on : 10/04/2017
  • Build ID
    :   v1.0.2
  • Chhi Score
    :   1.0
  • Change Rate
    :   0%

What to fix?

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

Your App Memory 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

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

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.

1 Risk(s) are due to Data Sent/Received in Network exceeding the threshold.

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

18 tests need immediate attention. View performance graph.

The app took 4.67 seconds to load on Android OS version 5.0.2. Usually anything more than 3.2 seconds results in user drops. View details

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

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

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

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

64.06 MB of App Dalvik utilized by activity com.zee.techno.apps.zee.music.player.activities.DMPlayerBaseActivity. View details

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

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

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

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

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

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

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

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

Caching: Use LruCache for data caching to optimize memory usage

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

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

Screen Coverage

competition benchmark

This app is ranked #895 in Music & Audio

890
891
892
893
894
back-to-top