App Quality Dashboard

Ripple Player

1.1 / 5

Chhi Score

This app is performing

Poor

Medium Risk

/5

High Risk

/5

Good 

/5

Medium Risk

/5

#

 

Category

Rank

  • Install time: Icon 13.64 Sec
  • Launch time: Icon 8.21 Sec
  • Application size: Icon 5.66 MB
  • Last tested on : 12/06/2017
  • Build ID
    :   v1.655
  • Chhi Score
    :   1.1
  • Change Rate
    :   0%

What to fix?

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

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.

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

Fixing CPU risks could drastically improve Chhi Score. There are 25 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

Build v1.654 did better in Memory . Spikes in Memory contributed to score drop by 5.71%

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

The app's Network score has improved by 50% compared to build v1.654! Good job!

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

25 tests need immediate attention. View performance graph.

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

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

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

Caching: Use LruCache for data caching to optimize memory usage

65.32 MB of App Dalvik utilized by activity com.enya.mprp.activity.SearchActivity. View details

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

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

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.

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

278 apps having similar CPU load have low Chhi Scores

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

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!

Well done, Network consumption has come down by 44.71 % compared to build v1.654

Screen Coverage

competition benchmark

This app is ranked #883 in Music & Audio

878
879
880
881
882
back-to-top