App Quality Dashboard

Piano +

3.7 / 5

Chhi Score

This app is performing

Average

Medium Risk

/5

Medium Risk

/5

Good 

/5

Medium Risk

/5

#

 

Category

Rank

  • Install time: Icon 22.00 Sec
  • Launch time: Icon 10.98 Sec
  • Application size: Icon 13.46 MB
  • Last tested on : 25/03/2017
  • Build ID
    :   v20170312
  • Chhi Score
    :   3.7
  • Change Rate
    :   -13.95 %

What to fix?

Build v20170222 did better in CPU . Spikes in CPU contributed to score drop by 41.46%

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

Build v20170222 did better in Memory . Spikes in Memory contributed to score drop by 22.73%

Build v20170222 did better in Network . Spikes in Network contributed to score drop by 42%

2 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.

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

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

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

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

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

4 tests need immediate attention. View performance graph.

Consider re-merging the code from build v20170222, Network score was 5.0

Consider re-merging the code from build v20170222, CPU score was 4.1

Consider re-merging the code from build v20170222, Memory score was 4.4

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

Network utilization on Motorola Moto E (2nd gen) exceeded 1024 KB, you might want to consider bringing it down

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

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

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

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

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

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

58.09 MB of App Dalvik utilized by activity com.google.android.gms.ads.AdActivity. View details

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

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

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

Caching: Use LruCache for data caching to optimize memory usage

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

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

Your average App Dalvik usage surged by 56.09%, Your memory score is 3.4

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

Total Network data consumed was 1547.69KB in Motorola Moto E (2nd gen) , This indicates the app will take 10-15 seconds on 2G network and 8-9 seconds on 3G network to load! View details

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

Screen Coverage

competition benchmark

This app is ranked #197 in Music & Audio

192
193
194
195
196
back-to-top