App Quality Dashboard

Otodom

0.3 / 5

Chhi Score

This app is performing

Poor

High Risk

/5

Medium Risk

/5

Good 

/5

Good

/5

#

 

Category

Rank

  • Install time: Icon 29.90 Sec
  • Launch time: Icon 1.59 Sec
  • Application size: Icon 14.14 MB
  • Last tested on : 21/02/2017
  • Build ID
    :   1.12.0
  • Chhi Score
    :   0.3
  • Change Rate
    :   0%

What to fix?

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

Your App Memory 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

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

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.

App launch time went up by 39.47% initlizate network calls after few seconds of loading the resources. View details

The app's CPU score has improved by 26.32% compared to build 1.11.2! Good job!

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

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

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

App size increased by 24.47% See how to optimize.

20 tests need immediate attention. View performance graph.

Utilization of CPU is close to the threshold.

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!

51.00 MB of App Dalvik utilized by activity 90. View details

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

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

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.

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

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

Caching: Use LruCache for data caching to optimize memory usage

The app's Network score has improved by 2.17% compared to build 1.11.2! Good job!

competition benchmark

This app is ranked #3457 in Lifestyle

3452
3453
3454
3455
3456
back-to-top