App Quality Dashboard


3.2 / 5

Chhi Score

This app is performing


Medium Risk


Medium Risk










  • Install time: Icon 16.50 Sec
  • Launch time: Icon 0.95 Sec
  • Application size: Icon 13.66 MB
  • Last tested on : 14/06/2017
  • Build ID
    :   v3.0.37
  • Chhi Score
    :   3.2
  • Change Rate
    :   -5.88 %

What to fix?

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.35 did better in Memory . Spikes in Memory contributed to score drop by 6.06%

The app's CPU score has improved by 3.33% compared to build v3.0.35! Good job!

4 tests need immediate attention. View performance graph.

App size increased by 122.11% See how to optimize.

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

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

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

52.20 MB of App Dalvik utilized by activity app.dodomerchants.activities.SplashNewActivity. View details

Your average App Dalvik usage surged by 3.57%, Your memory score is 3.1

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

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

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

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!

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

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

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

Well done, Network consumption has come down by 70.47 % compared to build v3.0.35

The app's Network score has improved by 2.08% compared to build v3.0.35! Good job!

Screen Coverage

competition benchmark

This app is ranked #261 in Maps & Navigation