App Quality Dashboard

Calendar Ortodox

3.9 / 5

Chhi Score

This app is performing

Average

Memory

Medium Risk

/5

CPU

Medium Risk

/5

crash

Good 

/5

network

Good

/5

Competition

#

 

Category

Rank

  • Install time: Icon 5.63 Sec
  • Launch time: Icon 1.50 Sec
  • Application size: --- 3.09 MB
  • Last tested on : 06/05/2017
  • Build ID
    :   v2.8.7
  • Chhi Score
    :   3.9
  • Change Rate
    :   +105.26 %

Insights (24)

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.
Fixing CPU risks could drastically improve Chhi Score. There are 5 CPU risks.
5 Risk(s) are due to Threads in CPU exceeding the threshold.
App launch time went up by INF% initlizate network calls after few seconds of loading the resources. View details
The app's CPU score has improved by 61.54% compared to build v2.8.6! Good job!
5 tests need immediate attention. View performance graph.
The app has a high performance risk for the phone manufacturer(s) InFocus, HTC. Check coverage report for more details.
Do not initialize objects that aren't necessary during launch times. Moving to singleton pattern helps
Fix & Optimize launch time using Flatbuffers for storage and rendering performance.
39.36 MB of App Dalvik utilized by activity ro.dcgavril.calendarortodox.MainListActivity. View details
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.
Testability: Providing login / sign-up details could very well improve depth of bot clicks
Optimize the app to render elements at 60 FPS for buttery smooth experience.
Below 10 MB approach would increase app installs in crowded markets such as India, China and Russia!
There is high probability of identifying risks running the apps with conditions
Fix Oncreate() if the launch time is exceeding more than 3.2 secs. Try deflating views and layouts to optimize.
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
Caching: Use LruCache for data caching to optimize memory usage
Avoid wake-locks in background, using Batch and schedulers APIs such as GCM, Job schedulers could reduce wake-locks
Well done, Network consumption has come down by 31.51 % compared to build v2.8.6
The app's Network score has improved by 4.65% compared to build v2.8.6! Good job!
The app's Memory score has improved by 27.59% compared to build v2.8.6! Good job!
Unlock more fixes

Screen Coverage

competition benchmark

This app is ranked #643 in Lifestyle

638
639
640
641
642
back-to-top