App Quality Dashboard


3.9 / 5

Chhi Score

This app is performing


Medium Risk


Medium Risk










  • Install time: Icon 43.20 Sec
  • Launch time: Icon 0.89 Sec
  • Application size: Icon 24.68 MB
  • Last tested on : 25/03/2017
  • Build ID
    :   v1.6.109
  • Chhi Score
    :   3.9
  • Change Rate
    :   0%

What to fix?

Build 1.6.96 did better in CPU . Spikes in CPU contributed to score drop by 26.92%

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

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.

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

Build 1.6.96 did better in Memory . Spikes in Memory contributed to score drop by 11.9%

Consider re-merging the code from build 1.6.96, CPU score was 2.6

App size increased by 26.76% See how to optimize.

9 tests need immediate attention. View performance graph.

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

Your average App Dalvik usage surged by 12.46%, Your memory score is 3.7

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

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

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

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

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

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

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

60.67 MB of App Dalvik utilized by activity com.facebook.FacebookActivity. View details

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!

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

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

The app's Network score has improved by 5% compared to build 1.6.96! Good job!

Well done, Network consumption has come down by 17.11 % compared to build 1.6.96

Screen Coverage

competition benchmark

This app is ranked #349 in Entertainment