App Quality Dashboard

eDreams

2.8 / 5

Chhi Score

This app is performing

Average

Medium Risk

/5

Medium Risk

/5

Good 

/5

Good

/5

#

 

Category

Rank

  • Install time: Icon 33.88 Sec
  • Launch time: Icon 0.83 Sec
  • Application size: Icon 19.91 MB
  • Last tested on : 04/05/2017
  • Build ID
    :   v4.5.1
  • Chhi Score
    :   2.8
  • Change Rate
    :   +40 %

What to fix?

8 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

Build v4.4.2 did better in Memory . Spikes in Memory contributed to score drop by 18.75%

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

17 tests need immediate attention. View performance graph.

Consider re-merging the code from build v4.4.2, Memory score was 3.2

Utilization of CPU is close to the threshold.

The app's CPU score has improved by 31.25% compared to build v4.4.2! Good job!

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

Caching: Use LruCache for data caching to optimize memory usage

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

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

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.

78.19 MB of App Dalvik utilized by activity com.odigeo.app.android.navigator.TravellersNavigator. View details

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

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

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

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

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

Your average App Dalvik usage surged by 1.25%, Your memory score is 2.6

competition benchmark

This app is ranked #673 in Travel & Local

668
669
670
671
672
back-to-top