App Quality Dashboard


2.4 / 5

Chhi Score

This app is performing


Medium Risk


Medium Risk










  • Install time: Icon 8.78 Sec
  • Launch time: Icon 1.40 Sec
  • Application size: --- 3.20 MB
  • Last tested on : 29/04/2017
  • Build ID
    :   v3.09.03
  • Chhi Score
    :   2.4
  • Change Rate
    :   -7.69 %

What to fix?

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

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

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

Build v3.09.02 did better in Memory . Spikes in Memory contributed to score drop by 8.7%

22 tests need immediate attention. View performance graph.

Utilization of CPU is close to the threshold.

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

Build v3.09.02 did better in Network . Spikes in Network contributed to score drop by 4.55%

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

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

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

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

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

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

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

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

50.95 MB of App Dalvik utilized by activity com.szyk.diabetes.MainActivity. View details

Caching: Use LruCache for data caching to optimize memory usage

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

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

Your average App Dalvik usage surged by 4.65%, Your memory score is 2.1

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

Screen Coverage

competition benchmark

This app is ranked #531 in Medical