App Quality Dashboard

Bicharada

3.4 / 5

Chhi Score

This app is performing

Average

Medium Risk

/5

Medium Risk

/5

Medium  Risk

/5

Medium Risk

/5

#

 

Category

Rank

  • Install time: 32.50 Sec
  • Launch time: 4.00 Sec
  • Application size : 46.38 MB
  • Last tested on : 29/04/2017
  • Build ID
    :   v2.0.1
  • Chhi Score
    :   3.4
  • Change Rate
    :   0%

What to fix?

Zenfone 2 Laser crashed at android.content.res.Resources.openRawResourceFd(Resources.java:1330) View details

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

Must fix: App crashed because of FATAL EXCEPTION: main Process: br.com.ajatec.bichos PID: 19077 android.content.res.Resources$No... 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.ajatec.bichos PID: 19077 android.content.res.Resources$No... 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.ajatec.bichos PID: 19077 android.content.res.Resources$No... Users with phone manufactured by Lenovo might experience a crash on their phone!. Fix now!

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

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.ajatec.bichos PID: 19077 android.content.res.Resources$No... 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.ajatec.bichos PID: 19077 android.content.res.Resources$No... 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.ajatec.bichos PID: 19077 android.content.res.Resources$No... Users with phone manufactured by Panasonic might experience a crash on their phone!. Fix now!

Motorola Moto E (2nd gen) crashed at android.content.res.Resources.openRawResourceFd(Resources.java:1315) View details

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 CPU risks could drastically improve Chhi Score. There are 13 CPU risks.

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

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

13 tests need immediate attention. View performance graph.

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

Utilization of Memory is close to the threshold.

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

Utilization of CPU is close to the threshold.

305.39 MB of App Dalvik utilized by activity br.pinceld.activity.GaleriaImagensActivity. View details

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

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

6 Tests crashed out of 26 Tests. Check where the app crashed. View details

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

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

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

Total Network data consumed was 2387.38KB in Zenfone 2 Laser , This indicates the app will take 10-15 seconds on 2G network and 8-9 seconds on 3G network to load! View details

Network utilization on Zenfone 2 Laser exceeded 1024 KB, you might want to consider bringing it down

Network utilization on Karbonn Titanium Machfive exceeded 1024 KB, you might want to consider bringing it down

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

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!

Caching: Use LruCache for data caching to optimize memory usage

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

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

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

Screen Coverage

competition benchmark

This app is ranked #834 in Education

829
830
831
832
833
back-to-top