App Quality Dashboard

Compass With Maps

3.1 / 5

Chhi Score

This app is performing

Average

Medium Risk

/5

Medium Risk

/5

Good 

/5

Medium Risk

/5

#

 

Category

Rank

  • Install time: 15.50 Sec
  • Launch time: 1.19 Sec
  • Application size : 5.18 MB
  • Last tested on : 16/05/2017
  • Build ID
    :   v1.1
  • Chhi Score
    :   3.1
  • Change Rate
    :   0%

What to fix?

3 Risk(s) are due to App PSS in Memory exceeding the threshold. See how to optimize memory and remove 3 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.

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

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

Utilization of CPU is close to the threshold.

3 tests need immediate attention. View performance graph.

50.93 MB of App Dalvik utilized by activity com.MapsNavigation.CompassWithMaps.MainActivity1. View details

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

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

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

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

Optimize the app to render elements at 60 FPS for buttery smooth experience.

Network utilization on LYF-WATER exceeded 1024 KB, you might want to consider bringing it down

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

Fix & Optimize launch time using Flatbuffers for storage and rendering performance.

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

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

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

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

Screen coverage

competition benchmark

This app is ranked #294 in Maps & Navigation

289
290
291
292
293
back-to-top