App Quality Dashboard

Blood Sugar Scanner

3.9 / 5

Chhi Score

This app is performing


Medium Risk


Medium Risk




Medium Risk






  • Install time: Icon 4.18 Sec
  • Launch time: Icon 0.62 Sec
  • Application size: Icon 2.58 MB
  • Last tested on : 09/05/2017
  • Build ID
    :   v1.5
  • Chhi Score
    :   3.9
  • Change Rate
    :   +2.63 %

What to fix?

Build v1.4 did better in CPU . Spikes in CPU contributed to score drop by 7.89%

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

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

Build v1.4 did better in Network . Spikes in Network contributed to score drop by 14.63%

Utilization of CPU is close to the threshold.

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

Consider re-merging the code from build v1.4, Network score was 4.1

10 tests need immediate attention. View performance graph.

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

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

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

33.76 MB of App Dalvik utilized by activity com.citylife.sugarrblod.MainActivity. View details

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

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

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

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

Fix & Optimize launch time using Flatbuffers for storage and rendering 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

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!

The app's Memory score has improved by 2.7% compared to build v1.4! Good job!

competition benchmark

This app is ranked #135 in Medical