App Quality Dashboard

Ładny Dom

3.9 / 5

Chhi Score

This app is performing

Average

Memory

Good

/5

CPU

Medium Risk

/5

crash

Good 

/5

network

Medium Risk

/5

Competition

#

 

Category

Rank

  • Install time: Icon 11.80 Sec
  • Launch time: Icon 1.38 Sec
  • Application size: Icon 10.69 MB
  • Last tested on : 13/05/2017
  • Build ID
    :   v1.1.1.0
  • Chhi Score
    :   3.9
  • Change Rate
    :   +69.57 %

Insights (28)

What to fix?

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.
2 Risk(s) are due to Data Sent/Received in Network exceeding the threshold.
6 Risk(s) are due to Threads in CPU exceeding the threshold.
Build v1.0.37.0 did better in Network . Spikes in Network contributed to score drop by 14.63%
7 tests need immediate attention. View performance graph.
Consider re-merging the code from build v1.0.37.0, Network score was 4.1
The app has a high performance risk for the phone manufacturer(s) HTC, Samsung, InFocus. Check coverage report for more details.
The app's CPU score has improved by 31.25% compared to build v1.0.37.0! Good job!
Network utilization on Samsung Galaxy S Duos 2 S7582 exceeded 1024 KB, you might want to consider bringing it down
Fix & Optimize launch time using Flatbuffers for storage and rendering performance.
Caching: Use LruCache for data caching to optimize memory usage
App makes 1027.66 KB of network requests. Moving this to a background thread will improve load speed. View details
Upload APKs with and without 3rd Party SDKs to monitor and optimize the impact of app performance
Network utilization on InFocus exceeded 1024 KB, you might want to consider bringing it down
Total Network data consumed was 1027.66KB in Samsung Galaxy S Duos 2 S7582 , This indicates the app will take 10-15 seconds on 2G network and 8-9 seconds on 3G network to load! View details
There is high probability of identifying risks running the apps with conditions
Avoid wake-locks in background, using Batch and schedulers APIs such as GCM, Job schedulers could reduce wake-locks
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.
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.
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.
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
47.32 MB of App Dalvik utilized by activity pl.agora.app.base.presentation.view.mainactivity.MainActivity. View details
The app's Memory score has improved by 16.22% compared to build v1.0.37.0! Good job!
Unlock more fixes

Screen Coverage

competition benchmark

This app is ranked #605 in Lifestyle

600
601
602
603
604
back-to-top