App Quality Dashboard

Baby Piano

1.4 / 5

Chhi Score

This app is performing

Poor

Medium Risk

/5

Medium Risk

/5

Good 

/5

High Risk

/5

#

 

Category

Rank

  • Install time: Icon 16.55 Sec
  • Launch time: Icon 2.34 Sec
  • Application size: Icon 17.88 MB
  • Last tested on : 08/05/2017
  • Build ID
    :   v00.00.05
  • Chhi Score
    :   1.4
  • Change Rate
    :   -50 %

What to fix?

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

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

Build v00.00.04 did better in Memory . Spikes in Memory contributed to score drop by 23.08%

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

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

Build v00.00.04 did better in CPU . Spikes in CPU contributed to score drop by 8.7%

Potential risk in Network: Utilization has gone up by74.47% compared to build v00.00.04

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.

Utilization of Network is close to the threshold.

9 tests need immediate attention. View performance graph.

Consider re-merging the code from build v00.00.04, Network score was 4.7

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

Utilization of CPU is close to the threshold.

Consider re-merging the code from build v00.00.04, Memory score was 2.6

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

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

61.27 MB of App Dalvik utilized by activity com.happytree.apps.babypiano.MainActivity. View details

Network utilization on Lava Iris X8 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

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

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

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

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

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

Caching: Use LruCache for data caching to optimize memory usage

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.

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

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

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

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

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

Screen Coverage

competition benchmark

This app is ranked #2187 in Education

2182
2183
2184
2185
2186
back-to-top