App Quality Dashboard

Korea Subway

2.2 / 5

Chhi Score

This app is performing

Average

Memory

Medium Risk

/5

CPU

Medium Risk

/5

crash

Medium  Risk

/5

network

Good

/5

Competition

#

 

Category

Rank

  • Install time: Icon 11.94 Sec
  • Launch time: Icon 2.54 Sec
  • Application size: --- 4.46 MB
  • Last tested on : 06/05/2017
  • Build ID
    :   v3.6.6
  • Chhi Score
    :   2.2
  • Change Rate
    :   +29.41 %

Insights (28)

What to fix?

Build v3.6.5 did better in Memory . Spikes in Memory contributed to score drop by 7.69%
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.
11 Risk(s) are due to Threads in CPU exceeding the threshold.
Must fix: App crashed because of FATAL EXCEPTION: UpdateCheck Process: com.kfmes.subway PID: 10580 java.lang.NullPointerExceptio... Users with phone manufactured by Samsung might experience a crash on their phone!. Fix now!
Fixing CPU risks could drastically improve Chhi Score. There are 11 CPU risks.
The app has a high performance risk for the phone manufacturer(s) Panasonic, Samsung, Lenovo, Karbonn, LYF, Lava. Check coverage report for more details.
Utilization of CPU is close to the threshold.
The app's CPU score has improved by 35.29% compared to build v3.6.5! Good job!
13 tests need immediate attention. View performance graph.
Lenovo A6000, Lava Iris X8, Samsung Duos Galaxy J7 has moved from Good to Medium risk due to FAIL . View details
Below 10 MB approach would increase app installs in crowded markets such as India, China and Russia!
Fix & Optimize launch time using Flatbuffers for storage and rendering performance.
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
53.23 MB of App Dalvik utilized by activity com.kfmes.subway.RouteActivity. View details
There is high probability of identifying risks running the apps with conditions
Printing logs on callbacks would make debugging easy for tests run in our platform
The app has crashed on few device(s)! View 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
3 Tests crashed out of 16 Tests. Check where the app crashed. View details
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
Upload APKs with and without 3rd Party SDKs to monitor and optimize the impact of app performance
Optimize the app to render elements at 60 FPS for buttery smooth experience.
The app's Network score has improved by 4.65% compared to build v3.6.5! Good job!
Well done, Network consumption has come down by 27.22 % compared to build v3.6.5
Unlock more fixes

Screen Coverage

competition benchmark

This app is ranked #914 in Travel & Local

909
910
911
912
913
back-to-top