App Quality Dashboard

Distance Finder

2.8 / 5

Chhi Score

This app is performing

Average

Memory

Medium Risk

/5

CPU

Medium Risk

/5

crash

Good 

/5

network

Good

/5

Competition

#

 

Category

Rank

  • Install time: Icon 6.70 Sec
  • Launch time: Icon 3.00 Sec
  • Application size: Icon 2.30 MB
  • Last tested on : 24/03/2017
  • Build ID
    :   v1.1
  • Chhi Score
    :   2.8
  • Change Rate
    :   +47.37 %

Insights (25)

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.
Fixing CPU risks could drastically improve Chhi Score. There are 11 CPU risks.
Build v1.0 did better in Memory . Spikes in Memory contributed to score drop by 13.79%
11 Risk(s) are due to Threads in CPU exceeding the threshold.
20 tests need immediate attention. View performance graph.
The app's CPU score has improved by 5.26% compared to build v1.0! Good job!
The app has a high performance risk for the phone manufacturer(s) Karbonn, Motorola, Lenovo, YU, Asus, Micromax, Panasonic. Check coverage report for more details.
Utilization of CPU is close to the threshold.
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!
Follow simple UI hierarchy by reducing nested layouts to Relative layouts.
Optimize the app to render elements at 60 FPS for buttery smooth experience.
Do not initialize objects that aren't necessary during launch times. Moving to singleton pattern helps
40.85 MB of App Dalvik utilized by activity com.androidutils.distancefinder.TwoLocationsActivity. View details
Upload APKs with and without 3rd Party SDKs to monitor and optimize the impact of app performance
Fix Oncreate() if the launch time is exceeding more than 3.2 secs. Try deflating views and layouts to optimize.
Printing logs on callbacks would make debugging easy for tests run in our platform
Your average App Dalvik usage surged by 2.75%, Your memory score is 2.5
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
Avoid wake-locks in background, using Batch and schedulers APIs such as GCM, Job schedulers could reduce wake-locks
Fix & Optimize launch time using Flatbuffers for storage and rendering performance.
There is high probability of identifying risks running the apps with conditions
Well done, Network consumption has come down by 83.35 % compared to build v1.0
The app's Network score has improved by 250% compared to build v1.0! Good job!
Unlock more fixes

Screen Coverage

competition benchmark

This app is ranked #347 in Maps & Navigation

342
343
344
345
346
back-to-top