App Quality Dashboard

Elevation and Sea Depth

3.3 / 5

Chhi Score

This app is performing


Medium Risk


Medium Risk










  • Install time: Icon 10.06 Sec
  • Launch time: Icon 2.80 Sec
  • Application size: Icon 2.74 MB
  • Last tested on : 24/04/2017
  • Build ID
    :   v3.0.2
  • Chhi Score
    :   3.3
  • Change Rate
    :   -2.94 %

What to fix?

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

Build v2.1.1 did better in Memory . Spikes in Memory contributed to score drop by 3.13%

Build v2.1.1 did better in CPU . Spikes in CPU contributed to score drop by 10.34%

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

7 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.

App size increased by 204.44% See how to optimize.

8 tests need immediate attention. View performance graph.

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

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

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!

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

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

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

43.04 MB of App Dalvik utilized by activity biz.binarysolutions.elevation.MainActivity. View details

Caching: Use LruCache for data caching to optimize memory usage

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

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

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

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

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

Your average App Dalvik usage surged by 4.83%, Your memory score is 3.1

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

Well done, Network consumption has come down by 49.12 % compared to build v2.1.1

The app's Network score has improved by 17.95% compared to build v2.1.1! Good job!

competition benchmark

This app is ranked #1104 in Tools