App Quality Dashboard

BMW Museum

1.6 / 5

Chhi Score

This app is performing

Poor

Memory

Medium Risk

/5

CPU

Medium Risk

/5

crash

Good 

/5

network

High Risk

/5

Competition

#

 

Category

Rank

  • Install time: 20.36 Sec
  • Launch time: 2.93 Sec
  • Application size : 16.04 MB
  • Last tested on : 02/05/2017
  • Build ID
    :   v1.2.0
  • Chhi Score
    :   1.6
  • Change Rate
    :   0%

Insights (25)

What to fix?

Fixing Network risks could drastically improve Chhi Score. There are 10 Network risks.
10 Risk(s) are due to Data Sent/Received in Network 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.
The app's memory score is 2.4 due to high memory utilization. Needs to be fixed as priority.
The app has a high performance risk for the phone manufacturer(s) YU, LYF, Lava, Motorola, Karbonn, Asus, Lenovo. Check coverage report for more details.
Utilization of CPU is close to the threshold.
21 tests need immediate attention. View performance graph.
Optimize the app to render elements at 60 FPS for buttery smooth experience.
Fix & Optimize launch time using Flatbuffers for storage and rendering performance.
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
Total Network data consumed was 5787.26KB in Lenovo A6000 , This indicates the app will take 10-15 seconds on 2G network and 8-9 seconds on 3G network to load! View details
Testability: Providing login / sign-up details could very well improve depth of bot clicks
Network utilization on Lava Iris X8 exceeded 1024 KB, you might want to consider bringing it down
87.56 MB of App Dalvik utilized by activity com.bmw.museum.ui.activity.MainActivity. View details
Network utilization on Lenovo A6000 exceeded 1024 KB, you might want to consider bringing it down
Avoid wake-locks in background, using Batch and schedulers APIs such as GCM, Job schedulers could reduce wake-locks
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
Follow simple UI hierarchy by reducing nested layouts to Relative layouts.
Below 10 MB approach would increase app installs in crowded markets such as India, China and Russia!
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
Fix Oncreate() if the launch time is exceeding more than 3.2 secs. Try deflating views and layouts to optimize.
App makes 5787.26 KB of network requests. Moving this to a background thread will improve load speed. View details
Unlock more fixes
competition benchmark

This app is ranked #2113 in Education

2108
2109
2110
2111
2112
back-to-top