App Quality Dashboard

Transantiago Bus Checker

0.9 / 5

Chhi Score

This app is performing


High Risk


High Risk


Medium  Risk








  • Install time: Icon 10.88 Sec
  • Launch time: Icon 2.37 Sec
  • Application size: --- 6.76 MB
  • Last tested on : 20/05/2017
  • Build ID
    :   v3.5.9
  • Chhi Score
    :   0.9
  • Change Rate
    :   +28.57 %

What to fix?

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

Potential risk in Memory: Utilization has gone up by16.67% compared to build v3.5.7

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

Must fix: App crashed because of 324): FATAL EXCEPTION: main 324): Process: com.fatattitude.buscheckersonda PID: 324 324): j... Users with phone manufactured by Samsung might experience a crash on their phone!. Fix now!

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

Your App Memory 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

Motorola Moto E (2nd gen), Zenfone 2 Laser , Panasonic P55 has moved from Good to Medium risk due to RISK . View details

21 tests need immediate attention. View performance graph.

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

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

85.43 MB of App Dalvik utilized by activity com.fatattitude.buschecker.ui.activity.TransitMapActivity. View details

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

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

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

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

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

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

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

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

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

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

120 apps having similar CPU load have low Chhi Scores

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

Well done, Network consumption has come down by 16.7 % compared to build v3.5.7

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

Screen Coverage

competition benchmark

This app is ranked #478 in Maps & Navigation