App Quality Dashboard

JustRide

2.9 / 5

Chhi Score

This app is performing

Average

Medium Risk

/5

Medium Risk

/5

Good 

/5

Good

/5

#

 

Category

Rank

  • Install time: Icon 17.93 Sec
  • Launch time: Icon 0.76 Sec
  • Application size: Icon 7.23 MB
  • Last tested on : 29/04/2017
  • Build ID
    :   v3.4.1
  • Chhi Score
    :   2.9
  • Change Rate
    :   -14.71 %

What to fix?

Build v3.5.6 did better in Memory . Spikes in Memory contributed to score drop by 12.12%

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

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.

The app's CPU score has improved by 6.67% compared to build v3.5.6! Good job!

Utilization of CPU is close to the threshold.

The app has a high performance risk for the phone manufacturer(s) YU, Motorola, LYF, Karbonn, Panasonic, Lenovo. Check coverage report for more details.

6 tests need immediate attention. View performance graph.

57.13 MB of App Dalvik utilized by activity in.justride.MainActivity. 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

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

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

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

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

Caching: Use LruCache for data caching to optimize memory usage

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

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

Well done, Network consumption has come down by 49.13 % compared to build v3.5.6

The app's Network score has improved by 2.13% compared to build v3.5.6! Good job!

Screen Coverage

competition benchmark

This app is ranked #635 in Travel & Local

630
631
632
633
634
back-to-top