App Quality Dashboard

Cycling VJ

1.7 / 5

Chhi Score

This app is performing

Poor

Memory

Medium Risk

/5

CPU

Medium Risk

/5

crash

High  Risk

/5

network

Good

/5

Competition

#

 

Category

Rank

  • Install time: 19.89 Sec
  • Launch time: 2.90 Sec
  • Application size : 25.70 MB
  • Last tested on : 17/06/2017
  • Build ID
    :   v1.4
  • Chhi Score
    :   1.7
  • Change Rate
    :   0%

Insights (29)

What to fix?

Must fix: App crashed because of FATAL EXCEPTION: main Process: com.quasar.eoxi.cyclingvjtw PID: 12335 com.facebook.FacebookEx... Users with phone manufactured by Lenovo might experience a crash on their phone!. Fix now!
Must fix: App crashed because of FATAL EXCEPTION: main Process: com.quasar.eoxi.cyclingvjtw PID: 12335 com.facebook.FacebookEx... Users with phone manufactured by Panasonic might experience a crash on their phone!. Fix now!
Must fix: App crashed because of FATAL EXCEPTION: main Process: com.quasar.eoxi.cyclingvjtw PID: 12335 com.facebook.FacebookEx... Users with phone manufactured by YU might experience a crash on their phone!. Fix now!
Must fix: App crashed because of FATAL EXCEPTION: main Process: com.quasar.eoxi.cyclingvjtw PID: 12335 com.facebook.FacebookEx... Users with phone manufactured by Lenovo might experience a crash on their phone!. Fix now!
Lenovo A6000 crashed at android.app.ActivityThread.performDestroyActivity(ActivityThread.java:3683) View details
Must fix: App crashed because of FATAL EXCEPTION: main Process: com.quasar.eoxi.cyclingvjtw PID: 12335 com.facebook.FacebookEx... Users with phone manufactured by Samsung might experience a crash on their phone!. Fix now!
Must fix: App crashed because of FATAL EXCEPTION: main Process: com.quasar.eoxi.cyclingvjtw PID: 12335 com.facebook.FacebookEx... Users with phone manufactured by Asus might experience a crash on their phone!. Fix now!
Must fix: App crashed because of FATAL EXCEPTION: main Process: com.quasar.eoxi.cyclingvjtw PID: 12335 com.facebook.FacebookEx... Users with phone manufactured by Motorola might experience a crash on their phone!. Fix now!
Must fix: App crashed because of FATAL EXCEPTION: main Process: com.quasar.eoxi.cyclingvjtw PID: 12335 com.facebook.FacebookEx... Users with phone manufactured by LYF might experience a crash on their phone!. Fix now!
Must fix: App crashed because of FATAL EXCEPTION: main Process: com.quasar.eoxi.cyclingvjtw PID: 12335 com.facebook.FacebookEx... Users with phone manufactured by Micromax might experience a crash on their phone!. Fix now!
Oops!, The app crashed on Motorola Moto E (2nd gen), Lenovo A6000 & more devices. View details
Motorola Moto E (2nd gen) crashed at com.facebook.widget.WebDialog$BuilderBase.(SourceFile:485) View details
The app has a high performance risk for the phone manufacturer(s) Panasonic, YU, LYF, Lenovo, Micromax, Samsung, Asus, Motorola. Check coverage report for more details.
Utilization of CPU is close to the threshold.
Coverage: Android version coverage for reports will range between 5.1.1 to 7.1.2
9 Tests crashed out of 27 Tests. Check where the app crashed. View details
Optimize the app to render elements at 60 FPS for buttery smooth experience.
There is high probability of identifying risks running the apps with conditions
Caching: Use LruCache for data caching to optimize memory usage
Testability: Providing login / sign-up details could very well improve depth of bot clicks
62.53 MB of App Dalvik utilized by activity com.quasar.eoxi.cyclingvjtw.PlayActivity. View details
Do not initialize objects that aren't necessary during launch times. Moving to singleton pattern helps
Avoid wake-locks in background, using Batch and schedulers APIs such as GCM, Job schedulers could reduce wake-locks
Upload APKs with and without 3rd Party SDKs to monitor and optimize the impact of app performance
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!
Fix & Optimize launch time using Flatbuffers for storage and rendering performance.
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
Unlock more fixes

Screen Coverage

competition benchmark

This app is ranked #1090 in Health & Fitness

1085
1086
1087
1088
1089
back-to-top