App Quality Dashboard

Call Ambulance

3.1 / 5

Chhi Score

This app is performing


Medium Risk


Medium Risk










  • Install time: Icon 19.85 Sec
  • Launch time: Icon 1.10 Sec
  • Application size: Icon 10.77 MB
  • Last tested on : 18/03/2017
  • Build ID
    :   v2.4.3
  • Chhi Score
    :   3.1
  • Change Rate
    :   -24.39 %

What to fix?

8 Risk(s) are due to App PSS in Memory exceeding the threshold. See how to optimize memory and remove 8 High Risk(s).

Build v2.4.2 did better in CPU . Spikes in CPU contributed to score drop by 24.39%

Build v2.4.2 did better in Memory . Spikes in Memory contributed to score drop by 26.83%

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.

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

Build v2.4.2 did better in Network . Spikes in Network contributed to score drop by 2.04%

Consider re-merging the code from build v2.4.2, Memory score was 4.1

Consider re-merging the code from build v2.4.2, CPU score was 4.1

Utilization of CPU is close to the threshold.

Utilization of Memory is close to the threshold.

8 tests need immediate attention. View performance graph.

65.20 MB of App Dalvik utilized by activity com.patientz.activity.RegistrationActivity. View details

Caching: Use LruCache for data caching to optimize memory usage

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

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

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

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

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

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.

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

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

Your average App Dalvik usage surged by 37.07%, Your memory score is 3.0

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

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

Screen coverage

competition benchmark

This app is ranked #381 in Medical