App Quality Dashboard

GO-JEK

3.9 / 5

Chhi Score

This app is performing

Average

Good

/5

Medium Risk

/5

Good 

/5

Good

/5

#

 

Category

Rank

  • Install time: Icon 49.73 Sec
  • Launch time: Icon 1.14 Sec
  • Application size: Icon 38.14 MB
  • Last tested on : 19/05/2017
  • Build ID
    :   v2.21.1
  • Chhi Score
    :   3.9
  • Change Rate
    :   -4.88 %

What to fix?

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 5 CPU risks.

Build v2.18.1 did better in CPU . Spikes in CPU contributed to score drop by 34.15%

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

App launch time went up by INF% initlizate network calls after few seconds of loading the resources. View details

Utilization of CPU is close to the threshold.

Consider re-merging the code from build v2.18.1, CPU score was 4.1

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

5 tests need immediate attention. View performance graph.

App size increased by 17.86% See how to optimize.

Build v2.18.1 did better in Network . Spikes in Network contributed to score drop by 2.13%

46.14 MB of App Dalvik utilized by activity com.gojek.app.profile.signup.SignUpActivity. View details

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

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

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!

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

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

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

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

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

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

Caching: Use LruCache for data caching to optimize memory usage

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

Screen Coverage

competition benchmark

This app is ranked #220 in Travel & Local

215
216
217
218
219
back-to-top