App Quality Dashboard

Chicago Transit Planner (CTA)

1.9 / 5

Chhi Score

This app is performing

Average

Medium Risk

/5

Medium Risk

/5

Medium  Risk

/5

Medium Risk

/5

#

 

Category

Rank

  • Install time: 19.13 Sec
  • Launch time: 3.00 Sec
  • Application size : 9.69 MB
  • Last tested on : 19/03/2017
  • Build ID
    :   v2.6
  • Chhi Score
    :   1.9
  • Change Rate
    :   0%

What to fix?

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

21 Risk(s) are due to Threads in CPU 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.

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

Must fix: App crashed because of 2394): FATAL EXCEPTION: main 2394): Process: in.applegends.chicago PID: 2394 2394): java.lang.V... Users with phone manufactured by Lava might experience a crash on their phone!. Fix now!

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

Utilization of CPU is close to the threshold.

21 tests need immediate attention. View performance graph.

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

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

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

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

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

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

106.63 MB of App Dalvik utilized by activity in.applegends.chicago.Selectstationname. View details

3 Tests crashed out of 24 Tests. Check where the app crashed. View details

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

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

The app has crashed on few device(s)! View details

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

Caching: Use LruCache for data caching to optimize memory usage

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

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

Network utilization on Lenovo VIBE K4 Note exceeded 1024 KB, you might want to consider bringing it down

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

Fix & Optimize launch time using Flatbuffers for storage and rendering performance.

competition benchmark

This app is ranked #966 in Travel & Local

961
962
963
964
965
back-to-top