App Quality Dashboard


3.4 / 5

Chhi Score

This app is performing


Medium Risk


Medium Risk










  • Install time: Icon 21.57 Sec
  • Launch time: Icon 6.22 Sec
  • Application size: Icon 7.82 MB
  • Last tested on : 26/04/2017
  • Build ID
    :   v3.2.2
  • Chhi Score
    :   3.4
  • Change Rate
    :   +9.68 %

What to fix?

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

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

10 Risk(s) are due to App PSS in Memory exceeding the threshold. See how to optimize memory and remove 10 High Risk(s).

11 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.

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

Utilization of CPU is close to the threshold.

Build v3.1.2 did better in Network . Spikes in Network contributed to score drop by 10.87%

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

The app's Memory score has improved by 6.9% compared to build v3.1.2! Good job!

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

1 Risk(s) are due to App Total in Memory exceeding the threshold.

15 tests need immediate attention. View performance graph.

The app's CPU score has improved by 9.52% compared to build v3.1.2! Good job!

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

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

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

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

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

59.00 MB of App Dalvik utilized by activity com.bigbasket.mobileapp.activity.SplashActivity. 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.

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

Caching: Use LruCache for data caching to optimize memory usage

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

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

Screen coverage

competition benchmark

This app is ranked #367 in Shopping