App Quality Dashboard

Musixmatch

0.6 / 5

Chhi Score

This app is performing

Poor

High Risk

/5

High Risk

/5

Good 

/5

Medium Risk

/5

#

 

Category

Rank

  • Install time: Icon 43.33 Sec
  • Launch time: Icon 15.73 Sec
  • Application size: --- 12.57 MB
  • Last tested on : 17/05/2017
  • Build ID
    :   v6.6.8
  • Chhi Score
    :   0.6
  • Change Rate
    :   -50 %

What to fix?

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

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

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 1062.75% initlizate network calls after few seconds of loading the resources. View details

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

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

Potential risk in Memory: Utilization has gone up by5.88% compared to build v6.6.7

Potential risk in CPU: Utilization has gone up by 33.33% compared to build v6.6.7

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

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

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

Build v6.6.7 did better in Network . Spikes in Network contributed to score drop by 5.26%

Consider re-merging the code from build v6.6.7, CPU score was 1.5

3 tests need immediate attention. View performance graph.

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

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

Caching: Use LruCache for data caching to optimize memory usage

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

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

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

278 apps having similar CPU load have low Chhi Scores

49.98 MB of App Dalvik utilized by activity o.Pp. View details

Your average App Dalvik usage surged by 41.85%, Your memory score is 1.6

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

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

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

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

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

Screen Coverage

competition benchmark

This app is ranked #956 in Music & Audio

951
952
953
954
955
back-to-top