App Quality Dashboard

DB Navigator

3.5 / 5

Chhi Score

This app is performing

Average

Medium Risk

/5

Medium Risk

/5

Good 

/5

Good

/5

#

 

Category

Rank

  • Install time: Icon 17.00 Sec
  • Launch time: Icon 0.85 Sec
  • Application size: Icon 16.45 MB
  • Last tested on : 04/05/2017
  • Build ID
    :   v17.04.p03.00
  • Chhi Score
    :   3.5
  • Change Rate
    :   +12.9 %

What to fix?

Build v16.12.p08.00 did better in CPU . Spikes in CPU contributed to score drop by 28%

Fixing CPU risks could drastically improve Chhi Score. There are 6 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.

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

Build v16.12.p08.00 did better in Network . Spikes in Network contributed to score drop by 2.13%

Utilization of CPU is close to the threshold.

The app's Memory score has improved by 10.34% compared to build v16.12.p08.00! Good job!

Consider re-merging the code from build v16.12.p08.00, CPU score was 2.5

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

6 tests need immediate attention. View performance graph.

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

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.

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

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

Caching: Use LruCache for data caching to optimize memory usage

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

51.50 MB of App Dalvik utilized by activity de.hafas.app.DashboardActivity. View details

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

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

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

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

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

Screen Coverage

competition benchmark

This app is ranked #213 in Maps & Navigation

208
209
210
211
212
back-to-top