App Quality Dashboard

GPS Route Finder

4.0 / 5

Chhi Score

This app is performing

Average

Medium Risk

/5

Medium Risk

/5

Good 

/5

Medium Risk

/5

#

 

Category

Rank

  • Install time: Icon 14.13 Sec
  • Launch time: Icon 6.92 Sec
  • Application size: Icon 8.06 MB
  • Last tested on : 19/05/2017
  • Build ID
    :   v2.0.10
  • Chhi Score
    :   4.0
  • Change Rate
    :   +2.56 %

What to fix?

Build v2.0.8 did better in Network . Spikes in Network contributed to score drop by 41.46%

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

App launch time went up by 2462.96% initlizate network calls after few seconds of loading the resources. View details

1 Risk(s) are due to Data Sent/Received in Network exceeding the threshold.

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.

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

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

The app took 6.92 seconds to load on Android OS version 5.0.2. Usually anything more than 3.2 seconds results in user drops. View details

App size increased by 16.47% See how to optimize.

Consider re-merging the code from build v2.0.8, Network score was 4.1

The app has a high performance risk for the phone manufacturer(s) Panasonic, Karbonn, Lava, LYF, Lenovo. Check coverage report for more details.

11 tests need immediate attention. View performance graph.

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

Utilization of CPU is close to the threshold.

52.96 MB of App Dalvik utilized by activity com.prime.studio.apps.route.finder.map.activity.MainActivity. View details

Network utilization on Lava Iris X8 exceeded 1024 KB, you might want to consider bringing it down

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

Total Network data consumed was 6094.92KB in Lava Iris X8 , This indicates the app will take 10-15 seconds on 2G network and 8-9 seconds on 3G network to load! View details

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

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

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

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

App makes 6094.92 KB of network requests. Moving this to a background thread will improve load speed. View details

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

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.

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

Caching: Use LruCache for data caching to optimize memory usage

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

Screen Coverage

competition benchmark

This app is ranked #589 in Tools

584
585
586
587
588
back-to-top