App Quality Dashboard

Happy Mama

4.0 / 5

Chhi Score

This app is performing


Medium Risk


Medium Risk










  • Install time: Icon 21.58 Sec
  • Launch time: Icon 0.47 Sec
  • Application size: Icon 14.30 MB
  • Last tested on : 30/04/2017
  • Build ID
    :   v1.16.5
  • Chhi Score
    :   4.0
  • Change Rate
    :   +66.67 %

What to fix?

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

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

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

11 tests need immediate attention. View performance graph.

Build v1.16.4 did better in Memory . Spikes in Memory contributed to score drop by 2.56%

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

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

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

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

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

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

Your average App Dalvik usage surged by 3.54%, Your memory score is 3.8

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!

35.54 MB of App Dalvik utilized by activity com.improve.baby_ru.view.SplashScreenActivity. View details

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.

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

Caching: Use LruCache for data caching to optimize memory usage

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

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

Well done, Network consumption has come down by 23.75 % compared to build v1.16.4

Screen coverage

competition benchmark

This app is ranked #121 in Medical