App Quality Dashboard

LaunchDay - FIFA 17 Edition

1.3 / 5

Chhi Score

This app is performing

Poor

Medium Risk

/5

Medium Risk

/5

Good 

/5

High Risk

/5

#

 

Category

Rank

  • Install time: 23.20 Sec
  • Launch time: 1.77 Sec
  • Application size : 25.63 MB
  • Last tested on : 05/05/2017
  • Build ID
    :   v2.1.0
  • Chhi Score
    :   1.3
  • Change Rate
    :   0%

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.

Fixing Network risks could drastically improve Chhi Score. There are 9 Network risks.

9 Risk(s) are due to Data Sent/Received in Network exceeding the threshold.

9 tests need immediate attention. View performance graph.

Utilization of CPU is close to the threshold.

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

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, LYF, Asus, Lenovo, Karbonn, YU, Micromax, Panasonic. Check coverage report for more details.

Network utilization on Motorola Moto E (2nd gen) exceeded 1024 KB, you might want to consider bringing it down

Caching: Use LruCache for data caching to optimize memory usage

36.72 MB of App Dalvik utilized by activity air.com.launchday.mobile.fifa.AppEntry. View details

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

Total Network data consumed was 4350.96KB in Motorola Moto E (2nd gen) , This indicates the app will take 10-15 seconds on 2G network and 8-9 seconds on 3G network to load! View details

App makes 4350.96 KB of network requests. Moving this to a background thread will improve load speed. View details

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

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

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

Network utilization on Lenovo A6000 exceeded 1024 KB, you might want to consider bringing it down

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

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.

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

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

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.

Screen Coverage

competition benchmark

This app is ranked #2162 in Entertainment

2157
2158
2159
2160
2161
back-to-top