App Quality Dashboard

My Scuba Experience

0.3 / 5

Chhi Score

This app is performing

Poor

High Risk

/5

Medium Risk

/5

Good 

/5

network

#

 

Category

Rank

  • Install time: 24.50 Sec
  • Launch time: 14.45 Sec
  • Application size : 40.99 MB
  • Last tested on : 06/05/2017
  • Build ID
    :   v1.0.0
  • Chhi Score
    :   0.3
  • Change Rate
    :   0%

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

The app's memory score is 0.5 due to high memory utilization. Needs to be fixed as priority.

22 tests need immediate attention. View performance graph.

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

Utilization of CPU is close to the threshold.

The app has a high performance risk for the phone manufacturer(s) Lava, YU, Micromax, Panasonic, Motorola, LYF, Lenovo, Samsung. 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

34.46 MB of App Dalvik utilized by activity com.eonreality.android.eonviewer.EONViewer. View details

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

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

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

Caching: Use LruCache for data caching to optimize memory usage

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

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

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.

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

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!

Screen Coverage

competition benchmark

This app is ranked #2318 in Education

2313
2314
2315
2316
2317
back-to-top