App Quality Dashboard

RailYatri

3.9 / 5

Chhi Score

This app is performing

Average

Good

/5

Medium Risk

/5

Good 

/5

Good

/5

#

 

Category

Rank

  • Install time: Icon 24.32 Sec
  • Launch time: Icon 1.17 Sec
  • Application size: Icon 11.92 MB
  • Last tested on : 18/05/2017
  • Build ID
    :   v3.2.0
  • Chhi Score
    :   3.9
  • Change Rate
    :   +62.5 %

What to fix?

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

1 Risk(s) are due to Data Sent/Received in Network exceeding the threshold.

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

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

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

The app's CPU score has improved by 50% compared to build v3.1.5! Good job!

9 tests need immediate attention. View performance graph.

Utilization of Network is close to the threshold.

Utilization of CPU is close to the threshold.

Caching: Use LruCache for data caching to optimize memory usage

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

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

42.07 MB of App Dalvik utilized by activity com.railyatri.in.activities.CityPreferencesActivity. View details

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

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

Network utilization on Panasonic P55 exceeded 1024 KB, you might want to consider bringing it down

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

App makes 1109.67 KB of network requests. Moving this to a background thread will improve load speed. View details

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

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

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

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

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

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

The app's Memory score has improved by 7.89% compared to build v3.1.5! Good job!

The app's Network score has improved by 2.44% compared to build v3.1.5! Good job!

competition benchmark

This app is ranked #233 in Travel & Local

228
229
230
231
232
back-to-top