App Quality Dashboard

Arriva Bus

3.9 / 5

Chhi Score

This app is performing

Average

Medium Risk

/5

Medium Risk

/5

Good 

/5

Good

/5

#

 

Category

Rank

  • Install time: Icon 12.40 Sec
  • Launch time: Icon 1.90 Sec
  • Application size: Icon 8.35 MB
  • Last tested on : 08/05/2017
  • Build ID
    :   v2.3.3 (29)
  • Chhi Score
    :   3.9
  • Change Rate
    :   0%

What to fix?

1 Risk(s) are due to Threads in CPU 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 2 CPU risks.

Build v2.3.2 (28) did better in CPU . Spikes in CPU contributed to score drop by 3.45%

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

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

Utilization of CPU is close to the threshold.

2 tests need immediate attention. View performance graph.

Caching: Use LruCache for data caching to optimize memory usage

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

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

104.12 MB of App Dalvik utilized by activity de.hafas.main.HafasApp. 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

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

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

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

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

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

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

The app's Memory score has improved by 5.26% compared to build v2.3.2 (28)! Good job!

Well done, Network consumption has come down by 21.5 % compared to build v2.3.2 (28)

Screen coverage

competition benchmark

This app is ranked #127 in Maps & Navigation

122
123
124
125
126
back-to-top