App Quality Dashboard


3.5 / 5

Chhi Score

This app is performing


Medium Risk


Medium Risk










  • Install time: Icon 18.67 Sec
  • Launch time: Icon 0.86 Sec
  • Application size: Icon 12.71 MB
  • Last tested on : 10/04/2017
  • Build ID
    :   v3.1.138
  • Chhi Score
    :   3.5
  • Change Rate
    :   -18.6 %

What to fix?

App launch time went up by 120.51% 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.

Build v3.0.25 did better in Memory . Spikes in Memory contributed to score drop by 18.6%

Build v3.0.25 did better in CPU . Spikes in CPU contributed to score drop by 17.07%

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

Consider re-merging the code from build v3.0.25, CPU score was 4.1

1 tests need immediate attention. View performance graph.

Consider re-merging the code from build v3.0.25, Memory score was 4.3

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

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

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

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

Caching: Use LruCache for data caching to optimize memory usage

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

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

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

48.41 MB of App Dalvik utilized by activity View details

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

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

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

Your average App Dalvik usage surged by 6.03%, Your memory score is 3.5

Well done, Network consumption has come down by 55.14 % compared to build v3.0.25

Screen Coverage

competition benchmark

This app is ranked #267 in Medical