App Quality Dashboard

Bíblia no Celular

1.8 / 5

Chhi Score

This app is performing

Average

Memory

Medium Risk

/5

CPU

Medium Risk

/5

crash

Medium  Risk

/5

network

High Risk

/5

Competition

#

 

Category

Rank

  • Install time: 19.00 Sec
  • Launch time: 5.00 Sec
  • Application size : 25.74 MB
  • Last tested on : 10/05/2017
  • Build ID
    :   v1.5.0
  • Chhi Score
    :   1.8
  • Change Rate
    :   0%

Insights (37)

What to fix?

Oops!, The app crashed on Zenfone 2 Laser , Motorola Moto E (2nd gen) & more devices. View details
Must fix: App crashed because of FATAL EXCEPTION: main Process: br.com.golmobile.biblianocelular PID: 14602 java.lang.IllegalArg... Users with phone manufactured by Asus might experience a crash on their phone!. Fix now!
Must fix: App crashed because of FATAL EXCEPTION: main Process: br.com.golmobile.biblianocelular PID: 14602 java.lang.IllegalArg... Users with phone manufactured by Karbonn might experience a crash on their phone!. Fix now!
Must fix: App crashed because of FATAL EXCEPTION: main Process: br.com.golmobile.biblianocelular PID: 14602 java.lang.IllegalArg... Users with phone manufactured by LYF might experience a crash on their phone!. Fix now!
Must fix: App crashed because of FATAL EXCEPTION: main Process: br.com.golmobile.biblianocelular PID: 14602 java.lang.IllegalArg... Users with phone manufactured by Motorola might experience a crash on their phone!. Fix now!
Must fix: App crashed because of FATAL EXCEPTION: main Process: br.com.golmobile.biblianocelular PID: 14602 java.lang.IllegalArg... Users with phone manufactured by Lenovo might experience a crash on their phone!. Fix now!
Motorola Moto E (2nd gen) crashed attached to window manager at android.view.WindowManagerGlobal.findViewLocked(WindowManagerGlobal.java:424) View details
Zenfone 2 Laser crashed attached to window manager at android.view.WindowManagerGlobal.findViewLocked(WindowManagerGlobal.java:424) View details
Fixing Network risks could drastically improve Chhi Score. There are 7 Network risks.
Must fix: App crashed because of FATAL EXCEPTION: main Process: br.com.golmobile.biblianocelular PID: 14602 java.lang.IllegalArg... Users with phone manufactured by Panasonic might experience a crash on their phone!. Fix now!
Must fix: App crashed because of FATAL EXCEPTION: main Process: br.com.golmobile.biblianocelular PID: 14602 java.lang.IllegalArg... Users with phone manufactured by Lava might experience a crash on their phone!. Fix now!
7 Risk(s) are due to Data Sent/Received in Network exceeding the threshold.
7 Risk(s) are due to App PSS in Memory exceeding the threshold. See how to optimize memory and remove 7 High Risk(s).
Utilization of Memory is close to the threshold.
The app took 5.00 seconds to load on Android OS version 5.0.2. Usually anything more than 3.2 seconds results in user drops. View details
1 Risk(s) are due to App Total in Memory exceeding the threshold.
The app has a high performance risk for the phone manufacturer(s) Karbonn, Panasonic, Motorola, Lenovo, LYF, Asus, Lava. Check coverage report for more details.
11 tests need immediate attention. View performance graph.
Total Network data consumed was 6612.01KB 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
Below 10 MB approach would increase app installs in crowded markets such as India, China and Russia!
Do not initialize objects that aren't necessary during launch times. Moving to singleton pattern helps
Network utilization on Zenfone 2 Laser 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
Network utilization on Motorola Moto E (2nd gen) exceeded 1024 KB, you might want to consider bringing it down
7 Tests crashed out of 27 Tests. Check where the app crashed. View details
Fix Oncreate() if the launch time is exceeding more than 3.2 secs. Try deflating views and layouts to optimize.
Caching: Use LruCache for data caching to optimize memory usage
There is high probability of identifying risks running the apps with conditions
Testability: Providing login / sign-up details could very well improve depth of bot clicks
Optimize the app to render elements at 60 FPS for buttery smooth experience.
Avoid wake-locks in background, using Batch and schedulers APIs such as GCM, Job schedulers could reduce wake-locks
74.17 MB of App Dalvik utilized by activity br.com.golmobile.biblianocelular.VideoPlayerActivity. View details
Follow simple UI hierarchy by reducing nested layouts to Relative layouts.
App makes 6612.01 KB of network requests. Moving this to a background thread will improve load speed. View details
Upload APKs with and without 3rd Party SDKs to monitor and optimize the impact of app performance
Fix & Optimize launch time using Flatbuffers for storage and rendering performance.
Printing logs on callbacks would make debugging easy for tests run in our platform
Unlock more fixes

Screen Coverage

competition benchmark

This app is ranked #1268 in Books & Reference

1263
1264
1265
1266
1267
back-to-top