App Quality Dashboard

RailRestro Mobile App

2.2 / 5

Chhi Score

This app is performing


Medium Risk


Medium Risk










  • Install time: Icon 5.38 Sec
  • Launch time: Icon 1.22 Sec
  • Application size: Icon 3.99 MB
  • Last tested on : 15/06/2017
  • Build ID
    :   v1.0.5
  • Chhi Score
    :   2.2
  • Change Rate
    :   -18.52 %

What to fix?

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

Build v1.0.4 did better in Memory . Spikes in Memory contributed to score drop by 23.08%

Build v1.0.4 did better in CPU . Spikes in CPU contributed to score drop by 3.57%

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.

7 tests need immediate attention. View performance graph.

App size increased by 22.39% See how to optimize.

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

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

Consider re-merging the code from build v1.0.4, Memory score was 2.6

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

42.24 MB of App Dalvik utilized by activity View details

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

Your average App Dalvik usage surged by 18%, Your memory score is 2.0

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

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

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

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

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

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

Caching: Use LruCache for data caching to optimize memory usage

Screen Coverage

competition benchmark

This app is ranked #293 in Food & Drink