App Quality Dashboard

IndiGo

2.7 / 5

Chhi Score

This app is performing

Average

Medium Risk

/5

Medium Risk

/5

Good 

/5

Medium Risk

/5

#

 

Category

Rank

  • Install time: Icon 38.86 Sec
  • Launch time: Icon 0.73 Sec
  • Application size: Icon 27.82 MB
  • Last tested on : 05/06/2017
  • Build ID
    :   v4.0.2
  • Chhi Score
    :   2.7
  • Change Rate
    :   +22.73 %

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.

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

5 tests need immediate attention. View performance graph.

The app's Memory score has improved by 19.05% compared to build v4.0.1! Good job!

Build v4.0.1 did better in Network . Spikes in Network contributed to score drop by 9.76%

Utilization of CPU is close to the threshold.

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

The app's memory score is 2.5 due to high memory utilization. Needs to be fixed as priority.

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

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.

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

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

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

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

19.34 MB of App Dalvik utilized by activity in.goindigo.android.MainActivity. View details

Caching: Use LruCache for data caching to optimize memory usage

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

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

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.

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

competition benchmark

This app is ranked #727 in Travel & Local

722
723
724
725
726
back-to-top