App Quality Dashboard

VK

0.1 / 5

Chhi Score

This app is performing

Poor

Memory

CPU

High  Risk

/5

network

#

 

Category

Rank

  • Install time: Icon 45.75 Sec
  • Launch time: --- 0.00 Sec
  • Application size: Icon 37.87 MB
  • Last tested on : 24/03/2017
  • Build ID
    :   v4.8.1
  • Chhi Score
    :   0.1
  • Change Rate
    :   0%

What to fix?

Must fix: App crashed because of FATAL EXCEPTION: main Process: com.vkontakte.android PID: 16794 java.lang.ExceptionInInitialize... Users with phone manufactured by Asus 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

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.

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 Zenfone 2 Laser , Samsung Duos Galaxy J7 & more devices. View details

Must fix: App crashed because of FATAL EXCEPTION: main Process: com.vkontakte.android PID: 16794 java.lang.ExceptionInInitialize... Users with phone manufactured by Samsung might experience a crash on their phone!. Fix now!

Zenfone 2 Laser crashed at java.lang.Class.classForName(Native Method) View details

Must fix: App crashed because of FATAL EXCEPTION: main Process: com.vkontakte.android PID: 16794 java.lang.ExceptionInInitialize... Users with phone manufactured by Lenovo might experience a crash on their phone!. Fix now!

Must fix: App crashed because of FATAL EXCEPTION: main Process: com.vkontakte.android PID: 16794 java.lang.ExceptionInInitialize... Users with phone manufactured by Panasonic might experience a crash on their phone!. Fix now!

Samsung Duos Galaxy J7 crashed at java.lang.Class.classForName(Native Method) View details

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

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

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

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

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

12 Tests crashed out of 12 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

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

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

Caching: Use LruCache for data caching to optimize memory usage

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!

213 apps having similar CPU load have low Chhi Scores

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

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

competition benchmark

This app is ranked #779 in Social

774
775
776
777
778
back-to-top