App Quality Dashboard

Practical Gastro

0.3 / 5

Chhi Score

This app is performing


High Risk


Medium Risk


Medium  Risk


High Risk






  • Install time: Icon 23.43 Sec
  • Launch time: Icon 1.37 Sec
  • Application size: Icon 8.55 MB
  • Last tested on : 08/05/2017
  • Build ID
    :   v32.0
  • Chhi Score
    :   0.3
  • Change Rate
    :   -76.92 %

What to fix?

Fixing Network risks could drastically improve Chhi Score. There are 14 Network risks.

Potential risk in Memory: Utilization has gone up by61.11% compared to build v27.0

14 Risk(s) are due to Data Sent/Received in Network 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.

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

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

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

Must fix: App crashed because of FATAL EXCEPTION: main java.lang.OutOfMemoryError at Users with phone manufactured by Samsung might experience a crash on their phone!. Fix now!

Utilization of CPU is close to the threshold.

App size increased by 45.41% See how to optimize.

Utilization of Memory is close to the threshold.

Make sure your App's PSS isn't too high. Freeing objects that aren't needed would reduce chances of getting unexpectedly killed by Android system.

14 tests need immediate attention. View performance graph.

11 Risk(s) are due to App Total in Memory exceeding the threshold.

Motorola Moto G 2014 XT1068 Dual 8GB, Motorola Moto E (2nd gen), Samsung Galaxy Note II N7100 has moved from Good to Medium risk due to RISK . View details

The app's memory score is 0.7 due to high memory utilization. Needs to be fixed as priority.

The app's CPU score has improved by 3.57% compared to build v27.0! Good job!

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

4 Risk(s) are due to App Dalvik in Memory exceeding the threshold.

Consider re-merging the code from build v27.0, Memory score was 1.8

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

Network utilization on Motorola Moto G 2014 XT1068 Dual 8GB exceeded 1024 KB, you might want to consider bringing it down

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

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

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

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

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

Total Network data consumed was 2514.79KB in Motorola Moto G 2014 XT1068 Dual 8GB , This indicates the app will take 10-15 seconds on 2G network and 8-9 seconds on 3G network to load! View details

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

72.02 MB of App Dalvik utilized by activity View details

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

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

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

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

Network utilization on Motorola Moto E (2nd gen) exceeded 1024 KB, you might want to consider bringing it down

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

Your average App Dalvik usage surged by 1.07%, Your memory score is 0.7

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

Caching: Use LruCache for data caching to optimize memory usage

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

Screen coverage

Test Flows YU Yuphoria Spice Mi-498 Dream Uno Panasonic P55 Novo Samsung Galaxy Note II N7100 Moto G (3rd Gen) Motorola Moto E (2nd gen) Motorola Moto G 2014 XT1068 Dual 8GB

Install app

  • Risk

  • Risk

  • Risk

  • Risk

  • Risk

  • Risk

  • Risk

Scenario 1

  • Risk

  • Risk

  • Crash

  • Risk

  • Risk

  • Risk

Scenario 2

  • Risk

competition benchmark

This app is ranked #672 in Medical