App Quality Dashboard


3.7 / 5

Chhi Score

This app is performing


Medium Risk


Medium Risk










  • Install time: Icon 43.04 Sec
  • Launch time: Icon 1.68 Sec
  • Application size: Icon 35.29 MB
  • Last tested on : 27/04/2017
  • Build ID
    :   v1.9.2.40
  • Chhi Score
    :   3.7
  • Change Rate
    :   -5.13 %

What to fix?

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

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

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

The app's CPU score has improved by 52.63% compared to build v1.9.2.38! Good job!

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

12 tests need immediate attention. View performance graph.

Utilization of CPU is close to the threshold.

Build v1.9.2.38 did better in Memory . Spikes in Memory contributed to score drop by 7.69%

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

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

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

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

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

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

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

Caching: Use LruCache for data caching to optimize memory usage

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

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

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.

61.02 MB of App Dalvik utilized by activity View details

The app's Network score has improved by 2.13% compared to build v1.9.2.38! Good job!

Well done, Network consumption has come down by 33.02 % compared to build v1.9.2.38

competition benchmark

This app is ranked #516 in Productivity