App Quality Dashboard

ooVoo

1.7 / 5

Chhi Score

This app is performing

Poor

Medium Risk

/5

Medium Risk

/5

Good 

/5

High Risk

/5

#

 

Category

Rank

  • Install time: Icon 32.40 Sec
  • Launch time: Icon 13.22 Sec
  • Application size: Icon 47.74 MB
  • Last tested on : 18/05/2017
  • Build ID
    :   v3.1.8
  • Chhi Score
    :   1.7
  • Change Rate
    :   0%

What to fix?

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

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

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

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.

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

Build v3.1.7 did better in CPU . Spikes in CPU contributed to score drop by 13.04%

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

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

Potential risk in Network: Utilization has gone up by29.41% compared to build v3.1.7

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

4 tests need immediate attention. View performance graph.

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

Make sure your App's PSS isn't too high. Freeing objects that aren't needed would reduce chances of getting unexpectedly killed by Android system.

Consider re-merging the code from build v3.1.7, Network score was 1.7

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

Utilization of Memory is close to the threshold.

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

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

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

Network utilization on Lenovo A6000 exceeded 1024 KB, you might want to consider bringing it down

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

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

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

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

Network utilization on Lenovo VIBE K4 Note exceeded 1024 KB, you might want to consider bringing it down

Caching: Use LruCache for data caching to optimize memory usage

67.19 MB of App Dalvik utilized by activity com.facebook.FacebookActivity. View details

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

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.

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

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

Screen coverage

Test Flows Lenovo VIBE K4 Note Lenovo A6000

Install app

  • Risk

  • Risk

Scenario 1

  • Risk

  • Success

Scenario 2

  • Risk

  • Success

competition benchmark

This app is ranked #661 in Social

656
657
658
659
660
back-to-top