App Quality Dashboard

Hot Topic

3.2 / 5

Chhi Score

This app is performing


Medium Risk


Medium Risk


Medium  Risk








  • Install time: Icon 21.56 Sec
  • Launch time: Icon 1.48 Sec
  • Application size: Icon 13.05 MB
  • Last tested on : 08/05/2017
  • Build ID
    :   v3.4.1
  • Chhi Score
    :   3.2
  • Change Rate
    :   -15.79 %

What to fix?

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

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

Build v3.3.09 did better in Memory . Spikes in Memory contributed to score drop by 2.78%

Must fix: App crashed because of 6955): FATAL EXCEPTION: main 6955): Process: PID: 6955 6955): java.lang.... Users with phone manufactured by Lava might experience a crash on their phone!. Fix now!

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.

Utilization of CPU is close to the threshold.

16 tests need immediate attention. View performance graph.

Motorola Moto E (2nd gen), Lava Iris X8, Panasonic P55 has moved from Good to Medium risk due to RISK . View details

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

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

App size increased by 20.28% See how to optimize.

3 Tests crashed out of 27 Tests. Check where the app crashed. View details

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

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

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

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

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

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

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

51.73 MB of App Dalvik utilized by activity View details

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

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

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

Well done, Network consumption has come down by 20.31 % compared to build v3.3.09

Screen Coverage

competition benchmark

This app is ranked #392 in Shopping