App Quality Dashboard

Scanner App

3.9 / 5

Chhi Score

This app is performing


Medium Risk


Medium Risk










  • Install time: Icon 18.60 Sec
  • Launch time: Icon 2.80 Sec
  • Application size: Icon 9.14 MB
  • Last tested on : 03/03/2017
  • Build ID
    :   v1.3.3
  • Chhi Score
    :   3.9
  • Change Rate
    :   -7.14 %

What to fix?

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

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

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.

Build 1.3.2 did better in CPU . Spikes in CPU contributed to score drop by 41.46%

4 tests need immediate attention. View performance graph.

Consider re-merging the code from build 1.3.2, CPU score was 4.1

Build 1.3.2 did better in Memory . Spikes in Memory contributed to score drop by 4.76%

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

Utilization of CPU is close to the threshold.

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

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

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

27.15 MB of App Dalvik utilized by activity mat.erial.activity.Main. View details

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

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

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

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

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

Caching: Use LruCache for data caching to optimize memory usage

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

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

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!

Well done, Network consumption has come down by 26.92 % compared to build 1.3.2

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

Screen Coverage

competition benchmark

This app is ranked #669 in Tools