App Quality Dashboard


1.0 / 5

Chhi Score

This app is performing


Medium Risk


High Risk


Medium  Risk








  • Install time: Icon 51.61 Sec
  • Launch time: Icon 14.88 Sec
  • Application size: Icon 35.06 MB
  • Last tested on : 10/10/2017
  • Build ID
    :   v6.0.1
  • Chhi Score
    :   1.0
  • Change Rate
    :   +11.11 %

What to fix?

Must fix: App crashed because of 941): java.lang.RuntimeException: here 941): at Users with phone manufactured by Panasonic might experience a crash on their phone!. Fix now!

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

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

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

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

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

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 size increased by 28.76% See how to optimize.

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

10 Risk(s) are due to CPU Load in CPU exceeding the threshold.

Lenovo A6000, Spice Mi-498 Dream Uno, Panasonic P55 has moved from Good to Medium risk due to RISK . View details

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

The app's Memory score has improved by 17.86% compared to build v5.2.4! Good job!

18 tests need immediate attention. View performance graph.

43.27 MB of App Dalvik utilized by activity View details

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

Caching: Use LruCache for data caching to optimize memory usage

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

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.

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

The app has crashed on few device(s)! View details

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

200 apps having similar CPU load have low Chhi Scores

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

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

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

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

Well done, Network consumption has come down by 73.7 % compared to build v5.2.4

The app's Network score has improved by 59.26% compared to build v5.2.4! Good job!

Screen Coverage

competition benchmark

This app is ranked #771 in Shopping