App Quality Dashboard

New York Subway

2.1 / 5

Chhi Score

This app is performing


Medium Risk


High Risk










  • Install time: Icon 21.80 Sec
  • Launch time: --- 4.00 Sec
  • Application size: Icon 14.58 MB
  • Last tested on : 26/04/2017
  • Build ID
    :   v2.3.0
  • Chhi Score
    :   2.1
  • Change Rate
    :   0%

What to fix?

Potential risk in CPU: Utilization has gone up by 38.89% compared to build v2.2.0

Fixing CPU risks could drastically improve Chhi Score. There are 26 CPU risks.

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.

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

Your App CPU is now in a High Risk Zone. With a small investment into your testing you can improve your app quality better. Get more test coverage

Build v2.2.0 did better in Memory . Spikes in Memory contributed to score drop by 2.94%

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

The app took 4.00 seconds to load on Android OS version 5.0.2. Usually anything more than 3.2 seconds results in user drops. View details

Utilization of CPU is close to the threshold.

Build v2.2.0 did better in Network . Spikes in Network contributed to score drop by 6.67%

26 tests need immediate attention. View performance graph.

Consider re-merging the code from build v2.2.0, CPU score was 1.8

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

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

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

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

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

60.32 MB of App Dalvik utilized by activity View details

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

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

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

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

120 apps having similar CPU load have low Chhi Scores

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

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

Screen Coverage

competition benchmark

This app is ranked #396 in Maps & Navigation