App Quality Dashboard

VR DO NC

0.9 / 5

Chhi Score

This app is performing

Poor

Memory

High Risk

/5

CPU

Medium Risk

/5

crash

Good 

/5

network

Competition

#

 

Category

Rank

  • Install time: 27.14 Sec
  • Launch time: 11.34 Sec
  • Application size : 40.41 MB
  • Last tested on : 06/05/2017
  • Build ID
    :   v3.0.0
  • Chhi Score
    :   0.9
  • Change Rate
    :   0%

Insights (24)

What to fix?

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
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
21 Risk(s) are due to App PSS in Memory exceeding the threshold. See how to optimize memory and remove 21 High Risk(s).
The app's memory score is 1.1 due to high memory utilization. Needs to be fixed as priority.
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.
21 tests need immediate attention. View performance graph.
3 Risk(s) are due to App Total in Memory exceeding the threshold.
The app took 11.34 seconds to load on Android OS version 5.0.2. Usually anything more than 3.2 seconds results in user drops. View details
The app has a high performance risk for the phone manufacturer(s) Asus, Panasonic, Motorola, YU, Lenovo, LYF. Check coverage report for more details.
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
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
There is high probability of identifying risks running the apps with conditions
Fix Oncreate() if the launch time is exceeding more than 3.2 secs. Try deflating views and layouts to optimize.
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.
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
Do not initialize objects that aren't necessary during launch times. Moving to singleton pattern helps
Below 10 MB approach would increase app installs in crowded markets such as India, China and Russia!
Caching: Use LruCache for data caching to optimize memory usage
34.68 MB of App Dalvik utilized by activity com.eonreality.android.eonviewer.EONViewer. View details
Unlock more fixes

Screen coverage

competition benchmark

This app is ranked #595 in Communication

590
591
592
593
594
back-to-top