App Quality Dashboard

GPS Route Finder

0.7 / 5

Chhi Score

This app is performing

Poor

Memory

Medium Risk

/5

CPU

Medium Risk

/5

crash

High  Risk

/5

network

Good

/5

Competition

#

 

Category

Rank

  • Install time: Icon 11.63 Sec
  • Launch time: Icon 0.63 Sec
  • Application size: Icon 6.14 MB
  • Last tested on : 27/05/2017
  • Build ID
    :   v1.3
  • Chhi Score
    :   0.7
  • Change Rate
    :   -77.42 %

Insights (27)

What to fix?

1 Risk(s) are due to Threads in CPU exceeding the threshold.
Must fix: App crashed because of 8995): FATAL EXCEPTION: main 8995): Process: com.jvstudios.gpstracker PID: 8995 8995): java.l... Users with phone manufactured by HTC might experience a crash on their phone!. Fix now!
Must fix: App crashed because of 8995): FATAL EXCEPTION: main 8995): Process: com.jvstudios.gpstracker PID: 8995 8995): java.l... Users with phone manufactured by Motorola might experience a crash on their phone!. Fix now!
Utilization of Memory is close to the threshold.
The app's Memory score has improved by 3.45% compared to build v1.0! Good job!
HTC Desire 626 Dual SIM, Motorola Nexus 6, HTC Desire 626 Dual SIM has moved from Good to Medium risk due to FAIL . View details
3 tests need immediate attention. View performance graph.
The app has a high performance risk for the phone manufacturer(s) Motorola, HTC, InFocus. Check coverage report for more details.
Avoid wake-locks in background, using Batch and schedulers APIs such as GCM, Job schedulers could reduce wake-locks
5 Tests crashed out of 8 Tests. Check where the app crashed. View details
Optimize the app to render elements at 60 FPS for buttery smooth experience.
150.08 MB of App Dalvik utilized by activity com.jvstudios.gpstracker.StartActivity. View details
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.
Follow simple UI hierarchy by reducing nested layouts to Relative layouts.
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
Do not initialize objects that aren't necessary during launch times. Moving to singleton pattern helps
Below 10 MB approach would increase app installs in crowded markets such as India, China and Russia!
There is high probability of identifying risks running the apps with conditions
Printing logs on callbacks would make debugging easy for tests run in our platform
Upload APKs with and without 3rd Party SDKs to monitor and optimize the impact of app performance
Fix & Optimize launch time using Flatbuffers for storage and rendering performance.
Caching: Use LruCache for data caching to optimize memory usage
Well done, Network consumption has come down by 41.58 % compared to build v1.0
The app's CPU score has improved by 25.81% compared to build v1.0! Good job!
The app's Network score has improved by 6.98% compared to build v1.0! Good job!
Unlock more fixes

Screen Coverage

competition benchmark

This app is ranked #1138 in Travel & Local

1133
1134
1135
1136
1137
back-to-top