App Quality Dashboard

Ross | dd’s

3.9 / 5

Chhi Score

This app is performing


Medium Risk


Medium Risk










  • Install time: Icon 31.70 Sec
  • Launch time: Icon 1.62 Sec
  • Application size: Icon 26.08 MB
  • Last tested on : 03/05/2017
  • Build ID
    :   v5.9
  • Chhi Score
    :   3.9
  • Change Rate
    :   +11.43 %

What to fix?

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

Build v4.17 did better in CPU . Spikes in CPU contributed to score drop by 9.09%

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

Utilization of CPU is close to the threshold.

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

7 tests need immediate attention. View performance graph.

Build v4.17 did better in Network . Spikes in Network contributed to score drop by 12.24%

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.

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

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

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

55.08 MB of App Dalvik utilized by activity com.crowdcompass.bearing.client.eventdirectory.controller.EventDirectoryController. View details

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

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

Caching: Use LruCache for data caching to optimize memory usage

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

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.

The app's Memory score has improved by 14.29% compared to build v4.17! Good job!

Screen Coverage

competition benchmark

This app is ranked #498 in Business