App Quality Dashboard

MTB Südtirol

0.2 / 5

Chhi Score

This app is performing

Poor

High Risk

/5

Medium Risk

/5

Medium  Risk

/5

Good

/5

#

 

Category

Rank

  • Install time: 25.10 Sec
  • Launch time: 0.76 Sec
  • Application size : 15.01 MB
  • Last tested on : 22/04/2017
  • Build ID
    :   v1.1
  • Chhi Score
    :   0.2
  • Change Rate
    :   0%

What to fix?

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

Must fix: App crashed because of 7740): FATAL EXCEPTION: AsyncTask #6 7740): Process: com.tappeiner.mtb_brixen PID: 7740 7740)... Users with phone manufactured by Lava might experience a crash on their phone!. Fix now!

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.

Your App Memory is now in a High Risk Zone. With a small investment into your testing you can improve your app quality better. Get more test coverage

27 tests need immediate attention. View performance graph.

Utilization of CPU is close to the threshold.

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

The app's memory score is 0.5 due to high memory utilization. Needs to be fixed as priority.

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

The app has crashed on few device(s)! View details

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

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

52.00 MB of App Dalvik utilized by activity 2246. View details

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

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

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

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

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

Caching: Use LruCache for data caching to optimize memory usage

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

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

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

Screen Coverage

competition benchmark

This app is ranked #1169 in Travel & Local

1164
1165
1166
1167
1168
back-to-top