App Quality Dashboard

Viber

2.0 / 5

Chhi Score

This app is performing

Average

Medium Risk

/5

High Risk

/5

Medium  Risk

/5

Good

/5

#

 

Category

Rank

  • Install time: Icon 64.00 Sec
  • Launch time: Icon 11.68 Sec
  • Application size: Icon 37.43 MB
  • Last tested on : 10/10/2017
  • Build ID
    :   v7.6.0.22
  • Chhi Score
    :   2.0
  • Change Rate
    :   -48.72 %

Testing depth

Covered

50%

Uncovered

50%

Depth Details

What to fix?

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

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

Must fix: App crashed because of 961): java.lang.RuntimeException: here 961): at com.android.server.am.ActivityManagerService.... Users with phone manufactured by Karbonn might experience a crash on their phone!. Fix now!

Fixing CPU risks could drastically improve Chhi Score. There are 19 CPU risks.

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

Lenovo A6000 crashed at java.io.DataInputStream.readByte(DataInputStream.java:77) View details

Potential risk in CPU: Utilization has gone up by 11.11% compared to build v6.8.7.8

Oops!, The app crashed on Karbonn Titanium Machfive, Lenovo A6000 & more devices. View details

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

Must fix: App crashed because of 961): java.lang.RuntimeException: here 961): at com.android.server.am.ActivityManagerService.... Users with phone manufactured by LYF might experience a crash on their phone!. Fix now!

App launch time went up by 63.77% initlizate network calls after few seconds of loading the resources. View details

Karbonn Titanium Machfive crashed at java.io.DataInputStream.readByte(DataInputStream.java:77) View details

Must fix: App crashed because of 961): java.lang.RuntimeException: here 961): at com.android.server.am.ActivityManagerService.... Users with phone manufactured by Lenovo 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.

17 tests need immediate attention. View performance graph.

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

Build v6.8.7.8 did better in Memory . Spikes in Memory contributed to score drop by 5.13%

Utilization of CPU is close to the threshold.

Build v6.8.7.8 did better in Network . Spikes in Network contributed to score drop by 4%

App size increased by 20.12% See how to optimize.

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

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

Samsung Duos Galaxy J7, YU Yuphoria, LYF-WATER has moved from Good to Medium risk due to RISK . View details

Utilization of Memory is close to the threshold.

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

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

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

48.33 MB of App Dalvik utilized by activity com.viber.voip.registration.SelectCountryActivity. View details

8 Tests crashed out of 34 Tests. Check where the app crashed. View details

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

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.

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

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

98 apps having similar CPU load have low Chhi Scores

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

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

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

Screen coverage

Test Flows YU Yuphoria LYF-WATER Karbonn Titanium Machfive Micromax Canvas AQ4502 Micromax Canvas Xpress Lenovo A6000 Samsung Duos Galaxy J7

Install app

  • Risk

  • Risk

  • Success

  • Success

  • Success

  • Success

  • Risk

Scenario 1

  • Risk

  • Risk

  • Crash

  • Risk

  • Risk

  • Crash

  • Risk

Scenario 2

  • Success

  • Risk

  • Crash

  • Risk

  • Success

  • Crash

  • Risk

Scenario 3

  • Risk

  • Risk

  • Crash

  • Risk

  • Success

  • Crash

  • Risk

Scenario 4

  • Success

  • Crash

  • Success

  • Risk

  • Crash

  • Risk

competition benchmark

This app is ranked #516 in Communication

511
512
513
514
515
back-to-top