App Quality Dashboard

Campus Compass

1.5 / 5

Chhi Score

This app is performing

Poor

Medium Risk

/5

Medium Risk

/5

Good 

/5

High Risk

/5

#

 

Category

Rank

  • Install time: Icon 22.43 Sec
  • Launch time: Icon 1.99 Sec
  • Application size: Icon 26.58 MB
  • Last tested on : 27/03/2017
  • Build ID
    :   v1.0.270
  • Chhi Score
    :   1.5
  • Change Rate
    :   +25 %

What to fix?

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

Build v1.0.262 did better in CPU . Spikes in CPU contributed to score drop by 7.41%

15 Risk(s) are due to App PSS in Memory exceeding the threshold. See how to optimize memory and remove 15 High Risk(s).

Fixing Network risks could drastically improve Chhi Score. There are 12 Network risks.

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

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

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.

App size increased by 10.7% See how to optimize.

15 tests need immediate attention. View performance graph.

The app's Memory score has improved by 4.76% compared to build v1.0.262! Good job!

Make sure your App's PSS isn't too high. Freeing objects that aren't needed would reduce chances of getting unexpectedly killed by Android system.

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

1 Risk(s) are due to CPU Load in CPU exceeding the threshold.

8 Risk(s) are due to App Total in Memory exceeding the threshold.

Utilization of CPU is close to the threshold.

Utilization of Memory is close to the threshold.

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

Avoid wake-locks in background, using Batch and schedulers APIs such as GCM, Job schedulers could reduce wake-locks

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

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

Caching: Use LruCache for data caching to optimize memory usage

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

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

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

Total Network data consumed was 5347.64KB in Motorola Moto E (2nd gen) , This indicates the app will take 10-15 seconds on 2G network and 8-9 seconds on 3G network to load! View details

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

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

Testability: Providing login / sign-up details could very well improve depth of bot clicks

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

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

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

90.17 MB of App Dalvik utilized by activity com.metroview.here.activities.MainActivity. View details

Network utilization on Motorola Moto E (2nd gen) exceeded 1024 KB, you might want to consider bringing it down

Well done, Network consumption has come down by 21.52 % compared to build v1.0.262

Screen coverage

competition benchmark

This app is ranked #443 in Maps & Navigation

438
439
440
441
442
back-to-top