App Quality Dashboard


3.0 / 5

Chhi Score

This app is performing


Medium Risk


Medium Risk




Medium Risk






  • Install time: Icon 7.32 Sec
  • Launch time: Icon 1.35 Sec
  • Application size: Icon 2.23 MB
  • Last tested on : 18/03/2017
  • Build ID
    :   v5.0.6
  • Chhi Score
    :   3.0
  • Change Rate
    :   -16.67 %

What to fix?

Build 5.0.5 did better in CPU . Spikes in CPU contributed to score drop by 20.69%

Build 5.0.5 did better in Memory . Spikes in Memory contributed to score drop by 22.86%

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

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

Build 5.0.5 did better in Network . Spikes in Network contributed to score drop by 34.15%

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.

Consider re-merging the code from build 5.0.5, Memory score was 3.5

Utilization of CPU is close to the threshold.

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

Consider re-merging the code from build 5.0.5, CPU score was 2.9

Consider re-merging the code from build 5.0.5, Network score was 4.1

1 Risk(s) are due to CPU Load in CPU exceeding the threshold.

17 tests need immediate attention. View performance graph.

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

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

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

Caching: Use LruCache for data caching to optimize memory usage

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

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

67.53 MB of App Dalvik utilized by activity View details

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

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

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

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

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

Your average App Dalvik usage surged by 36.25%, Your memory score is 2.7

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

Screen Coverage

competition benchmark

This app is ranked #618 in Travel & Local