App Quality Dashboard


3.3 / 5

Chhi Score

This app is performing


Medium Risk


Medium Risk




Medium Risk






  • Install time: Icon 25.00 Sec
  • Launch time: Icon 1.13 Sec
  • Application size: Icon 12.44 MB
  • Last tested on : 03/03/2017
  • Build ID
    :   v3.1.2
  • Chhi Score
    :   3.3
  • Change Rate
    :   -10.81 %

What to fix?

Build 3.0.4 did better in Memory . Spikes in Memory contributed to score drop by 16.67%

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.

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

Build 3.0.4 did better in Network . Spikes in Network contributed to score drop by 25.58%

Build 3.0.4 did better in CPU . Spikes in CPU contributed to score drop by 11.11%

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

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

Consider re-merging the code from build 3.0.4, Network score was 4.3

2 tests need immediate attention. View performance graph.

Consider re-merging the code from build 3.0.4, Memory score was 3.6

Utilization of Memory is close to the threshold.

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

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

Your average App Dalvik usage surged by 12.11%, Your memory score is 3.0

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

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

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.

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

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

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

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

33.96 MB of App Dalvik utilized by activity View details

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

Caching: Use LruCache for data caching to optimize memory usage

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

Screen coverage

competition benchmark

This app is ranked #395 in Social