App Quality Dashboard


2.9 / 5

Chhi Score

This app is performing


Medium Risk


Medium Risk










  • Install time: Icon 29.38 Sec
  • Launch time: Icon 1.21 Sec
  • Application size: Icon 15.60 MB
  • Last tested on : 03/05/2017
  • Build ID
    :   v8.08
  • Chhi Score
    :   2.9
  • Change Rate
    :   -9.38 %

What to fix?

Build v8.06 did better in CPU . Spikes in CPU contributed to score drop by 13.33%

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

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

Build v8.06 did better in Memory . Spikes in Memory contributed to score drop by 9.68%

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 tests need immediate attention. View performance graph.

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

Utilization of CPU is close to the threshold.

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

Utilization of Memory is close to the threshold.

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.

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

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

40.02 MB of App Dalvik utilized by activity com.truecaller.ui.WizardActivity. View details

Your average App Dalvik usage surged by 11.66%, Your memory score is 2.8

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

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

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

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

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

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

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

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

Well done, Network consumption has come down by 26.12 % compared to build v8.06

Screen coverage

Test Flows YU Yuphoria Lava Iris X8 LYF-WATER Karbonn Titanium Machfive Zenfone 2 Laser Motorola Moto E (2nd gen)

Install app

  • Success

  • Success

  • Success

  • Success

  • Risk

  • Risk

Scenario 1

  • Success

Scenario 2

  • Success

competition benchmark

This app is ranked #451 in Communication