App Quality Dashboard

Moody Media

2.9 / 5

Chhi Score

This app is performing


Medium Risk


Medium Risk




Medium Risk






  • Install time: Icon 17.50 Sec
  • Launch time: Icon 0.46 Sec
  • Application size: Icon 6.77 MB
  • Last tested on : 14/04/2017
  • Build ID
    :   v3.4.2
  • Chhi Score
    :   2.9
  • Change Rate
    :   -29.27 %

What to fix?

Build v3.1.0 did better in Memory . Spikes in Memory contributed to score drop by 31.71%

Build v3.1.0 did better in Network . Spikes in Network contributed to score drop by 17.07%

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

Build v3.1.0 did better in CPU . Spikes in CPU contributed to score drop by 4.88%

1 tests need immediate attention. View performance graph.

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

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

Utilization of Memory is close to the threshold.

Utilization of CPU is close to the threshold.

Consider re-merging the code from build v3.1.0, Network score was 4.1

Consider re-merging the code from build v3.1.0, Memory score was 4.1

App size increased by 31.2% See how to optimize.

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

Below 10 MB approach would increase app installs in crowded markets such as India, China and Russia!

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

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

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

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

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

37.24 MB of App Dalvik utilized by activity com.subsplash.thechurchapp.MainActivity. View details

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

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

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

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

Caching: Use LruCache for data caching to optimize memory usage

Well done, Network consumption has come down by 46.76 % compared to build v3.1.0

Screen coverage

competition benchmark

This app is ranked #1753 in Lifestyle