App Quality Dashboard


3.0 / 5

Chhi Score

This app is performing


Medium Risk


Medium Risk




Medium Risk






  • Install time: Icon 14.56 Sec
  • Launch time: Icon 3.83 Sec
  • Application size: Icon 6.06 MB
  • Last tested on : 09/03/2017
  • Build ID
    :   v13.0
  • Chhi Score
    :   3.0
  • Change Rate
    :   -11.76 %

What to fix?

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

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

Build v2.6 did better in Network . Spikes in Network contributed to score drop by 8.11%

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

Build v2.6 did better in Memory . Spikes in Memory contributed to score drop by 12.9%

The app took 3.83 seconds to load on Android OS version 5.0.2. Usually anything more than 3.2 seconds results in user drops. View details

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

8 tests need immediate attention. View performance graph.

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

The app's CPU score has improved by 15.79% compared to build v2.6! Good job!

49.13 MB of App Dalvik utilized by activity View details

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.

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

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

Caching: Use LruCache for data caching to optimize memory usage

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

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

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

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

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

Screen Coverage

competition benchmark

This app is ranked #789 in Productivity