App Quality Dashboard

Dumpster

0.9 / 5

Chhi Score

This app is performing

Poor

Medium Risk

/5

High Risk

/5

Good 

/5

Good

/5

#

 

Category

Rank

  • Install time: Icon 21.14 Sec
  • Launch time: Icon 1.77 Sec
  • Application size: Icon 9.83 MB
  • Last tested on : 28/02/2017
  • Build ID
    :   v2.13.254.9646
  • Chhi Score
    :   0.9
  • Change Rate
    :   -10 %

What to fix?

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.

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

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

Your App CPU is now in a High Risk Zone. With a small investment into your testing you can improve your app quality better. Get more test coverage

Build 2.11.246.7dc3 did better in Memory . Spikes in Memory contributed to score drop by 10%

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

21 tests need immediate attention. View performance graph.

App size increased by 28.66% See how to optimize.

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.

91.15 MB of App Dalvik utilized by activity com.baloota.dumpster.ui.onboarding.intro.DumpsterIntro. View details

144 apps having similar CPU load have low Chhi Scores

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

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.

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

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

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

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

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

Well done, Network consumption has come down by 76.7 % compared to build 2.11.246.7dc3

The app's Network score has improved by 173.33% compared to build 2.11.246.7dc3! Good job!

Screen Coverage

competition benchmark

This app is ranked #1052 in Productivity

1047
1048
1049
1050
1051
back-to-top