App Quality Dashboard

Opera beta

0.4 / 5

Chhi Score

This app is performing

Poor

High Risk

/5

High Risk

/5

Good 

/5

Medium Risk

/5

#

 

Category

Rank

  • Install time: 34.00 Sec
  • Launch time: 1.40 Sec
  • Application size : 42.15 MB
  • Last tested on : 13/04/2017
  • Build ID
    :   v42.7.2246.114995
  • Chhi Score
    :   0.4
  • 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).

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

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

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

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 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

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

The app has a high performance risk for the phone manufacturer(s) Karbonn, Samsung, 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.

4 tests need immediate attention. View performance graph.

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

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

40.94 MB of App Dalvik utilized by activity com.opera.android.BrowserActivity. View details

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

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

98 apps having similar CPU load have low Chhi Scores

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

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

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

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.

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

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

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

Screen coverage

Test Flows Karbonn Titanium Machfive Lenovo VIBE K4 Note Samsung Galaxy J7

Install app

  • Risk

  • Risk

  • Risk

Scenario 1

  • Success

Scenario 2

  • Risk

competition benchmark

This app is ranked #608 in Communication

603
604
605
606
607
back-to-top