App Quality Dashboard

Share & Add Places

2.5 / 5

Chhi Score

This app is performing


Medium Risk


Medium Risk




Medium Risk






  • Install time: Icon 12.00 Sec
  • Launch time: Icon 1.58 Sec
  • Application size: Icon 2.00 MB
  • Last tested on : 15/03/2017
  • Build ID
    :   v1.5
  • Chhi Score
    :   2.5
  • Change Rate
    :   -30.56 %

What to fix?

Build v1.3 did better in Memory . Spikes in Memory contributed to score drop by 28.13%

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.

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

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

Consider re-merging the code from build v1.3, Memory score was 3.2

3 tests need immediate attention. View performance graph.

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

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

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

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

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

20.58 MB of App Dalvik utilized by activity com.androidutils.locationbook.LocalLocationsActivity. View details

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

Your average App Dalvik usage surged by 22.6%, Your memory score is 2.3

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

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

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

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

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

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

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

Well done, Network consumption has come down by 59.7 % compared to build v1.3

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

competition benchmark

This app is ranked #356 in Maps & Navigation