App Quality Dashboard

Behance

1.0 / 5

Chhi Score

This app is performing

Poor

Medium Risk

/5

Medium Risk

/5

Medium  Risk

/5

Good

/5

#

 

Category

Rank

  • Install time: 30.38 Sec
  • Launch time: 2.63 Sec
  • Application size : 27.15 MB
  • Last tested on : 18/04/2017
  • Build ID
    :   v4.1.2
  • Chhi Score
    :   1.0
  • Change Rate
    :   0%

What to fix?

Motorola Moto E (2nd gen) crashed at dalvik.system.VMRuntime.newNonMovableArray(Native Method) View details

Oops!, The app crashed on Spice Mi-498 Dream Uno, Motorola Moto E (2nd gen) & more devices. View details

2 Risk(s) are due to App Dalvik in Memory exceeding the threshold. See how to optimize memory and remove 2 High Risk(s).

Must fix: App crashed because of FATAL EXCEPTION: main Process: com.behance.behance PID: 25692 java.lang.OutOfMemoryError: Faile... Users with phone manufactured by Motorola might experience a crash on their phone!. Fix now!

Spice Mi-498 Dream Uno crashed at dalvik.system.VMRuntime.newNonMovableArray(Native Method) View details

Must fix: App crashed because of FATAL EXCEPTION: main Process: com.behance.behance PID: 25692 java.lang.OutOfMemoryError: Faile... Users with phone manufactured by Micromax might experience a crash on their phone!. Fix now!

Must fix: App crashed because of FATAL EXCEPTION: main Process: com.behance.behance PID: 25692 java.lang.OutOfMemoryError: Faile... Users with phone manufactured by Spice 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.

Utilization of CPU is close to the threshold.

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

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

15 tests need immediate attention. View performance graph.

2 Risk(s) are due to App Dalvik in Memory exceeding the threshold.

Utilization of Memory is close to the threshold.

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

Caching: Use LruCache for data caching to optimize memory usage

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.

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

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

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

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

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

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

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

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

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

190.06 MB of App Dalvik utilized by activity com.behance.network.ui.activities.TourLiteActivity. View details

Screen Coverage

competition benchmark

This app is ranked #738 in Social

733
734
735
736
737
back-to-top