App Quality Dashboard

Maps and Directions - Navigator

3.3 / 5

Chhi Score

This app is performing


Medium Risk


Medium Risk


Medium  Risk








  • Install time: Icon 14.86 Sec
  • Launch time: Icon 0.62 Sec
  • Application size: Icon 6.85 MB
  • Last tested on : 20/05/2017
  • Build ID
    :   v1.1
  • Chhi Score
    :   3.3
  • Change Rate
    :   -5.71 %

What to fix?

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

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

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

Build v1.0 did better in CPU . Spikes in CPU contributed to score drop by 15.15%

Must fix: App crashed because of FATAL EXCEPTION: main Process: com.jvstudios.routeguide.places.nearme PID: 29580 java.lang.Runt... Users with phone manufactured by Motorola might experience a crash on their phone!. Fix now!

Consider re-merging the code from build v1.0, CPU score was 3.3

3 tests need immediate attention. View performance graph.

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

Utilization of CPU is close to the threshold.

The app's Memory score has improved by 9.09% compared to build v1.0! Good job!

Motorola Nexus 6, Motorola Nexus 6, HTC Desire 626 Dual SIM has moved from Good to Medium risk due to RISK . View details

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.

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

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

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

Caching: Use LruCache for data caching to optimize memory usage

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

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

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

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

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

The app has crashed on few device(s)! View details

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

78.40 MB of App Dalvik utilized by activity com.jvstudios.routeguide.places.nearme.StartActivity. View details

Well done, Network consumption has come down by 72.79 % compared to build v1.0

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

Screen Coverage

competition benchmark

This app is ranked #472 in Travel & Local