App Quality Dashboard

Baby Major Steps

2.1 / 5

Chhi Score

This app is performing


Medium Risk


Medium Risk




High Risk






  • Install time: Icon 16.58 Sec
  • Launch time: Icon 3.59 Sec
  • Application size: Icon 4.79 MB
  • Last tested on : 16/03/2017
  • Build ID
    :   v1.41
  • Chhi Score
    :   2.1
  • Change Rate
    :   -12.5 %

What to fix?

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

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

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

4 Risk(s) are due to App PSS in Memory exceeding the threshold. See how to optimize memory and remove 4 High Risk(s).

Potential risk in Network: Utilization has gone up by68.42% compared to build v1.39

Build v1.39 did better in Memory . Spikes in Memory contributed to score drop by 17.95%

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.

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

11 tests need immediate attention. View performance graph.

Consider re-merging the code from build v1.39, Memory score was 3.9

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

Utilization of Memory is close to the threshold.

Consider re-merging the code from build v1.39, Network score was 3.8

The app's CPU score has improved by 11.76% compared to build v1.39! Good job!

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

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

Caching: Use LruCache for data caching to optimize memory usage

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

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.

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

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

51.90 MB of App Dalvik utilized by activity com.everbum.blgm.ActivityConf. View details

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

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

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

Your average App Dalvik usage surged by 20.21%, Your memory score is 3.2

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

Total Network data consumed was 3419.26KB 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

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

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

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

Screen coverage

competition benchmark

This app is ranked #61 in Parenting