App Quality Dashboard

Instant Heart Rate

0.9 / 5

Chhi Score

This app is performing


Medium Risk


High Risk




Medium Risk






  • Install time: Icon 43.33 Sec
  • Launch time: Icon 44.51 Sec
  • Application size: Icon 38.89 MB
  • Last tested on : 17/06/2017
  • Build ID
    :   v5.36.3036
  • Chhi Score
    :   0.9
  • Change Rate
    :   -59.09 %

What to fix?

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

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

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

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

Build 5.36.2835 did better in Memory . Spikes in Memory contributed to score drop by 20.59%

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

Potential risk in CPU: Utilization has gone up by 23.08% compared to build 5.36.2835

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.

11 tests need immediate attention. View performance graph.

Consider re-merging the code from build 5.36.2835, Memory score was 3.4

App size increased by 32.87% See how to optimize.

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

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

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

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 7.52%, Your memory score is 2.7

Caching: Use LruCache for data caching to optimize memory usage

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

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

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

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

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

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

254 apps having similar CPU load have low Chhi Scores

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

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

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

76.33 MB of App Dalvik utilized by activity View details

The app's Network score has improved by 15.63% compared to build 5.36.2835! Good job!

Well done, Network consumption has come down by 32.25 % compared to build 5.36.2835

Screen Coverage

competition benchmark

This app is ranked #1302 in Health & Fitness