App Quality Dashboard

Ola Operator

3.0 / 5

Chhi Score

This app is performing

Average

Medium Risk

/5

Medium Risk

/5

Good 

/5

Good

/5

#

 

Category

Rank

  • Install time: Icon 12.78 Sec
  • Launch time: Icon 0.76 Sec
  • Application size: Icon 8.38 MB
  • Last tested on : 19/05/2017
  • Build ID
    :   v1.4.0.9
  • Chhi Score
    :   3.0
  • Change Rate
    :   -3.23 %

What to fix?

Build v1.4.0.6 did better in CPU . Spikes in CPU contributed to score drop by 11.11%

Build v1.4.0.6 did better in Memory . Spikes in Memory contributed to score drop by 3.45%

6 Risk(s) are due to App PSS in Memory exceeding the threshold. See how to optimize memory and remove 6 High Risk(s).

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

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.

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

8 tests need immediate attention. View performance graph.

Utilization of Memory is close to the threshold.

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

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

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

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

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

Your average App Dalvik usage surged by 10.89%, Your memory score is 2.8

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

74.42 MB of App Dalvik utilized by activity com.olacabs.android.operator.ui.landing.login.LoginActivity. View details

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

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

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.

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

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

Screen coverage

competition benchmark

This app is ranked #301 in Maps & Navigation

296
297
298
299
300
back-to-top