App Quality Dashboard


3.2 / 5

Chhi Score

This app is performing


Medium Risk


Medium Risk










  • Install time: Icon 37.48 Sec
  • Launch time: Icon 1.05 Sec
  • Application size: Icon 24.18 MB
  • Last tested on : 27/03/2017
  • Build ID
    :   v3.4
  • Chhi Score
    :   3.2
  • Change Rate
    :   -11.11 %

What to fix?

Build v3.3 did better in Memory . Spikes in Memory contributed to score drop by 11.43%

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

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.

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

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

10 tests need immediate attention. View performance graph.

Build v3.3 did better in Network . Spikes in Network contributed to score drop by 4.17%

Utilization of CPU is close to the threshold.

39.88 MB of App Dalvik utilized by activity com.tesco.clubcardmobile.activity.UserRegistrationActivity. View details

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

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

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

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

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

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

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

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

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

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

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

competition benchmark

This app is ranked #1320 in Lifestyle