App Quality Dashboard


3.0 / 5

Chhi Score

This app is performing


Medium Risk


Medium Risk









  • Install time: Icon 12.70 Sec
  • Launch time: Icon 2.33 Sec
  • Application size: Icon 4.84 MB
  • Last tested on : 24/04/2017
  • Build ID
    :   v0.0.5
  • Chhi Score
    :   3.0
  • Change Rate
    :   -11.76 %

What to fix?

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.

Build v0.0.4 did better in CPU . Spikes in CPU contributed to score drop by 17.14%

Build v0.0.4 did better in Memory . Spikes in Memory contributed to score drop by 23.53%

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

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

Consider re-merging the code from build v0.0.4, Memory score was 3.4

6 tests need immediate attention. View performance graph.

Consider re-merging the code from build v0.0.4, CPU score was 3.5

Utilization of CPU is close to the threshold.

Consider re-merging the code from build v0.0.4, Network score was 4.8

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

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

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

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

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

22.77 MB of App Dalvik utilized by activity com.appectual.twoMLaserService.MainActivity. View details

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

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

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

Your average App Dalvik usage surged by 59%, Your memory score is 2.6

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

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

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

Screen Coverage

competition benchmark

This app is ranked #408 in Medical