App Quality Dashboard

HomeCatcher

2.6 / 5

Chhi Score

This app is performing

Average

Medium Risk

/5

Medium Risk

/5

Good 

/5

network

#

 

Category

Rank

  • Install time: Icon 30.17 Sec
  • Launch time: Icon 0.54 Sec
  • Application size: Icon 38.94 MB
  • Last tested on : 09/04/2017
  • Build ID
    :   v0.6.2
  • Chhi Score
    :   2.6
  • Change Rate
    :   +4 %

What to fix?

Build v0.5.0 did better in CPU . Spikes in CPU contributed to score drop by 20.59%

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.

Build v0.5.0 did better in Memory . Spikes in Memory contributed to score drop by 12.5%

App size increased by 16.76% See how to optimize.

5 tests need immediate attention. View performance graph.

Consider re-merging the code from build v0.5.0, Network score was 4.6

Consider re-merging the code from build v0.5.0, CPU score was 3.4

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

Utilization of CPU is close to the threshold.

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

Caching: Use LruCache for data caching to optimize memory usage

41.13 MB of App Dalvik utilized by activity nl.rabobank.homecatcher.MainActivity. View details

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

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

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

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!

Your average App Dalvik usage surged by 45.46%, Your memory score is 2.1

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

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

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

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

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

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

Screen Coverage

competition benchmark

This app is ranked #2162 in Lifestyle

2157
2158
2159
2160
2161
back-to-top