App Quality Dashboard

Augsburg Navigator

3.8 / 5

Chhi Score

This app is performing


Medium Risk


Medium Risk










  • Install time: Icon 13.00 Sec
  • Launch time: Icon 3.62 Sec
  • Application size: --- 8.34 MB
  • Last tested on : 04/05/2017
  • Build ID
    :   v1.1.2b (39)
  • Chhi Score
    :   3.8
  • Change Rate
    :   -7.32 %

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.

Build 1.1.2 (24) did better in CPU . Spikes in CPU contributed to score drop by 29.27%

Consider re-merging the code from build 1.1.2 (24), CPU score was 4.1

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) Motorola, Lava. Check coverage report for more details.

Build 1.1.2 (24) did better in Memory . Spikes in Memory contributed to score drop by 9.76%

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

4 tests need immediate attention. View performance graph.

Utilization of CPU is close to the threshold.

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

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

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

Caching: Use LruCache for data caching to optimize memory usage

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

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

Your average App Dalvik usage surged by 4.51%, Your memory score is 3.7

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

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

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

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

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

62.35 MB of App Dalvik utilized by activity de.hafas.main.HafasApp. View details

Screen Coverage

competition benchmark

This app is ranked #152 in Maps & Navigation