App Quality Dashboard

Spider in phone

0.1 / 5

Chhi Score

This app is performing

Poor

Memory

CPU

High  Risk

/5

network

#

 

Category

Rank

  • Install time: 10.50 Sec
  • Launch time: 0.00 Sec
  • Application size : 7.49 MB
  • Last tested on : 16/06/2017
  • Build ID
    :   v2.0.2
  • Chhi Score
    :   0.1
  • Change Rate
    :   0%

What to fix?

Must fix: App crashed because of 5810): FATAL EXCEPTION: main 5810): Process: com.mandg.funny.spider PID: 5810 5810): java.lan... Users with phone manufactured by Asus might experience a crash on their phone!. Fix now!

Must fix: App crashed because of 5810): FATAL EXCEPTION: main 5810): Process: com.mandg.funny.spider PID: 5810 5810): java.lan... Users with phone manufactured by Panasonic might experience a crash on their phone!. Fix now!

Your App Memory is now in a High Risk Zone. With a small investment into your testing you can improve your app quality better. Get more test coverage

Zenfone 2 Laser crashed at java.lang.Runtime.loadLibrary(Runtime.java:367) View details

Your App CPU is now in a High Risk Zone. With a small investment into your testing you can improve your app quality better. Get more test coverage

Oops!, The app crashed on Panasonic P55, Zenfone 2 Laser & more devices. View details

Panasonic P55 crashed at java.lang.Runtime.loadLibrary(Runtime.java:367) 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.

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

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

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

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

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

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

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

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

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

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

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

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

508 apps having similar CPU load have low Chhi Scores

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

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

competition benchmark

This app is ranked #2418 in Entertainment

2413
2414
2415
2416
2417
back-to-top