App Quality Dashboard

BlaBlaCar

2.7 / 5

Chhi Score

This app is performing

Average

Medium Risk

/5

Medium Risk

/5

Good 

/5

Good

/5

#

 

Category

Rank

  • Install time: Icon 17.67 Sec
  • Launch time: Icon 0.95 Sec
  • Application size: Icon 16.08 MB
  • Last tested on : 18/05/2017
  • Build ID
    :   v4.24.1
  • Chhi Score
    :   2.7
  • Change Rate
    :   -34.15 %

What to fix?

Build v4.23.1 did better in Memory . Spikes in Memory contributed to score drop by 39.02%

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

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.

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

Build v4.23.1 did better in CPU . Spikes in CPU contributed to score drop by 43.9%

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

5 tests need immediate attention. View performance graph.

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

The app has a high performance risk for the phone manufacturer(s) Samsung, YU, Lava. Check coverage report for more details.

Utilization of CPU is close to the threshold.

Consider re-merging the code from build v4.23.1, CPU score was 4.1

Build v4.23.1 did better in Network . Spikes in Network contributed to score drop by 4%

Consider re-merging the code from build v4.23.1, Memory score was 4.1

40.72 MB of App Dalvik utilized by activity com.comuto.v3.activity.MainDrawerActivity. View details

Caching: Use LruCache for data caching to optimize memory usage

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

Fix & Optimize launch time using Flatbuffers for storage and rendering performance.

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

Upload APKs with and without 3rd Party SDKs to monitor and optimize the impact of app performance

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

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

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

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

Fix Oncreate() if the launch time is exceeding more than 3.2 secs. Try deflating views and layouts to optimize.

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

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 #732 in Travel & Local

727
728
729
730
731
back-to-top