App Quality Dashboard

Maps and Directions - Navigator

3.3 / 5

Chhi Score

This app is performing

Average

Memory

Medium Risk

/5

CPU

Medium Risk

/5

crash

Medium  Risk

/5

network

Good

/5

Competition

#

 

Category

Rank

  • 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 %

Insights (30)

What to fix?

Fixing CPU risks could drastically improve Chhi Score. There are 2 CPU risks.
Build v1.0 did better in CPU . Spikes in CPU contributed to score drop by 15.15%
2 Risk(s) are due to Threads in CPU exceeding the threshold.
App launch time went up by 40.91% initlizate network calls after few seconds of loading the resources. View details
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!
2 Risk(s) are due to App PSS in Memory exceeding the threshold. See how to optimize memory and remove 2 High Risk(s).
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.
The app has a high performance risk for the phone manufacturer(s) HTC, InFocus, Motorola. Check coverage report for more details.
The app's Memory score has improved by 9.09% compared to build v1.0! Good job!
3 tests need immediate attention. View performance graph.
Utilization of CPU is close to the threshold.
Consider re-merging the code from build v1.0, CPU score was 3.3
Motorola Nexus 6, Motorola Nexus 6, HTC Desire 626 Dual SIM has moved from Good to Medium risk due to RISK . View details
Upload APKs with and without 3rd Party SDKs to monitor and optimize the impact of app performance
The app has crashed on few device(s)! View details
Fix & Optimize launch time using Flatbuffers for storage and rendering performance.
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
Fix Oncreate() if the launch time is exceeding more than 3.2 secs. Try deflating views and layouts to optimize.
Caching: Use LruCache for data caching to optimize memory usage
Below 10 MB approach would increase app installs in crowded markets such as India, China and Russia!
78.40 MB of App Dalvik utilized by activity com.jvstudios.routeguide.places.nearme.StartActivity. View details
Coverage: Android version coverage for reports will range between 5.1.1 to 7.1.2
Printing logs on callbacks would make debugging easy for tests run in our platform
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.
Do not initialize objects that aren't necessary during launch times. Moving to singleton pattern helps
Optimize the app to render elements at 60 FPS for buttery smooth experience.
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!
Unlock more fixes

Screen coverage

competition benchmark

This app is ranked #472 in Travel & Local

467
468
469
470
471
back-to-top