App Quality Dashboard

Uber

2.5 / 5

Chhi Score

This app is performing

Average

Memory

Medium Risk

/5

CPU

Medium Risk

/5

crash

Good 

/5

network

Good

/5

Competition

#

 

Category

Rank

  • Install time: Icon 81.53 Sec
  • Launch time: Icon 5.00 Sec
  • Application size: Icon 53.00 MB
  • Last tested on : 18/05/2017
  • Build ID
    :   v3.151.5
  • Chhi Score
    :   2.5
  • Change Rate
    :   -21.88 %

Insights (28)

What to fix?

Build v3.149.3 did better in CPU . Spikes in CPU contributed to score drop by 28.57%
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.
Fixing CPU risks could drastically improve Chhi Score. There are 15 CPU risks.
15 Risk(s) are due to Threads in CPU exceeding the threshold.
Build v3.149.3 did better in Memory . Spikes in Memory contributed to score drop by 23.33%
Build v3.149.3 did better in Network . Spikes in Network contributed to score drop by 2.04%
The app took 5.00 seconds to load on Android OS version 5.0.2. 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) Motorola, Micromax, Lenovo, Panasonic, Asus, YU, Karbonn. Check coverage report for more details.
Consider re-merging the code from build v3.149.3, Memory score was 3.0
Consider re-merging the code from build v3.149.3, CPU score was 2.8
App size increased by 32.24% See how to optimize.
20 tests need immediate attention. View performance graph.
Coverage: Android version coverage for reports will range between 5.1.1 to 7.1.2
Do not initialize objects that aren't necessary during launch times. Moving to singleton pattern helps
78.16 MB of App Dalvik utilized by activity com.ubercab.presidio.app.core.root.RootActivity. View details
Follow simple UI hierarchy by reducing nested layouts to Relative layouts.
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
Testability: Providing login / sign-up details could very well improve depth of bot clicks
Fix & Optimize launch time using Flatbuffers for storage and rendering performance.
Avoid wake-locks in background, using Batch and schedulers APIs such as GCM, Job schedulers could reduce wake-locks
Your average App Dalvik usage surged by 43.25%, Your memory score is 2.3
Below 10 MB approach would increase app installs in crowded markets such as India, China and Russia!
Optimize the app to render elements at 60 FPS for buttery smooth experience.
Fix Oncreate() if the launch time is exceeding more than 3.2 secs. Try deflating views and layouts to optimize.
There is high probability of identifying risks running the apps with conditions
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 #359 in Maps & Navigation

354
355
356
357
358
back-to-top