App Quality Dashboard


2.9 / 5

Chhi Score

This app is performing


Medium Risk


Medium Risk










  • Install time: Icon 22.42 Sec
  • Launch time: Icon 5.82 Sec
  • Application size: Icon 27.46 MB
  • Last tested on : 07/05/2017
  • Build ID
    :   v9.7.890
  • Chhi Score
    :   2.9
  • Change Rate
    :   -29.27 %

What to fix?

Build v9.6.858 did better in Memory . Spikes in Memory contributed to score drop by 29.27%

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

Build v9.6.858 did better in Network . Spikes in Network contributed to score drop by 6%

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

5 tests need immediate attention. View performance graph.

Consider re-merging the code from build v9.6.858, Memory score was 4.1

The app took 5.82 seconds to load on Android OS version 5.0.2. Usually anything more than 3.2 seconds results in user drops. View details

Build v9.6.858 did better in CPU . Spikes in CPU contributed to score drop by 9.76%

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

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

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

43.95 MB of App Dalvik utilized by activity net.probki.cityguide.CityGuide. View details

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

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

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

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

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

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.

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

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

competition benchmark

This app is ranked #646 in Travel & Local