App Quality Dashboard

BBC Focus Magazine

1.8 / 5

Chhi Score

This app is performing

Average

Medium Risk

/5

Medium Risk

/5

High  Risk

/5

High Risk

/5

#

 

Category

Rank

  • Install time: 18.32 Sec
  • Launch time: 4.97 Sec
  • Application size : 10.58 MB
  • Last tested on : 09/05/2017
  • Build ID
    :   v5.3.6
  • Chhi Score
    :   1.8
  • Change Rate
    :   0%

What to fix?

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

Must fix: App crashed because of 8529): FATAL EXCEPTION: main 8529): Process: com.focus.magazine PID: 8529 8529): java.lang.Null... Users with phone manufactured by Lenovo might experience a crash on their phone!. Fix now!

Oops!, The app crashed on Motorola Moto E (2nd gen), Lenovo A6000 & more devices. View details

Must fix: App crashed because of 8529): FATAL EXCEPTION: main 8529): Process: com.focus.magazine PID: 8529 8529): java.lang.Null... Users with phone manufactured by Lenovo might experience a crash on their phone!. Fix now!

Lenovo A6000 crashed attached to Activity 5895): at android.support.v4.app.Fragment.getResources(Fragment.java:651) View details

Motorola Moto E (2nd gen) crashed attached to Activity at android.support.v4.app.Fragment.getResources(Fragment.java:651) View details

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

Must fix: App crashed because of 8529): FATAL EXCEPTION: main 8529): Process: com.focus.magazine PID: 8529 8529): java.lang.Null... Users with phone manufactured by Panasonic might experience a crash on their phone!. Fix now!

Must fix: App crashed because of 8529): FATAL EXCEPTION: main 8529): Process: com.focus.magazine PID: 8529 8529): java.lang.Null... Users with phone manufactured by Micromax might experience a crash on their phone!. Fix now!

Fixing CPU risks could drastically improve Chhi Score. There are 16 CPU risks.

Must fix: App crashed because of 8529): FATAL EXCEPTION: main 8529): Process: com.focus.magazine PID: 8529 8529): java.lang.Null... Users with phone manufactured by LYF might experience a crash on their phone!. Fix now!

Must fix: App crashed because of 8529): FATAL EXCEPTION: main 8529): Process: com.focus.magazine PID: 8529 8529): java.lang.Null... Users with phone manufactured by Motorola might experience a crash on their phone!. Fix now!

Must fix: App crashed because of 8529): FATAL EXCEPTION: main 8529): Process: com.focus.magazine PID: 8529 8529): java.lang.Null... Users with phone manufactured by Asus might experience a crash on their phone!. Fix now!

Must fix: App crashed because of 8529): FATAL EXCEPTION: main 8529): Process: com.focus.magazine PID: 8529 8529): java.lang.Null... Users with phone manufactured by YU 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.

Must fix: App crashed because of 8529): FATAL EXCEPTION: main 8529): Process: com.focus.magazine PID: 8529 8529): java.lang.Null... Users with phone manufactured by Karbonn might experience a crash on their phone!. Fix now!

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

11 Risk(s) are due to CPU Load in CPU exceeding the threshold.

Utilization of CPU is close to the threshold.

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

16 tests need immediate attention. View performance graph.

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

162.60 MB of App Dalvik utilized by activity com.immediate.imcreader.MainActivity. View details

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

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

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

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

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

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

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

10 Tests crashed out of 25 Tests. Check where the app crashed. View details

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

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

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

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

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

Total Network data consumed was 31465.04KB 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

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

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

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

Screen Coverage

competition benchmark

This app is ranked #992 in News & Magazines

987
988
989
990
991
back-to-top