App Quality Dashboard

Wook Reader

2.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 21.80 Sec
  • Launch time: Icon 1.37 Sec
  • Application size: Icon 22.48 MB
  • Last tested on : 11/04/2017
  • Build ID
    :   v02.06.04
  • Chhi Score
    :   2.9
  • Change Rate
    :   0%

Insights (25)

What to fix?

Build 02.04.02 did better in CPU . Spikes in CPU contributed to score drop by 16.13%
App launch time went up by 44.21% initlizate network calls after few seconds of loading the resources. View details
5 Risk(s) are due to App PSS in Memory exceeding the threshold. See how to optimize memory and remove 5 High Risk(s).
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 02.04.02 did better in Memory . Spikes in Memory contributed to score drop by 3.57%
Make sure your App's PSS isn't too high. Freeing objects that aren't needed would reduce chances of getting unexpectedly killed by Android system.
Utilization of CPU is close to the threshold.
The app has a high performance risk for the phone manufacturer(s) Micromax, Lenovo, YU, LYF. Check coverage report for more details.
5 tests need immediate attention. View performance graph.
Consider re-merging the code from build 02.04.02, CPU score was 3.1
Fix & Optimize launch time using Flatbuffers for storage and rendering performance.
29.16 MB of App Dalvik utilized by activity pt.portoeditora.wookreader.MainActivity. View details
Upload APKs with and without 3rd Party SDKs to monitor and optimize the impact of app performance
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
Your average App Dalvik usage surged by 15.41%, Your memory score is 2.7
Fix Oncreate() if the launch time is exceeding more than 3.2 secs. Try deflating views and layouts to optimize.
There is high probability of identifying risks running the apps with conditions
Optimize the app to render elements at 60 FPS for buttery smooth experience.
Caching: Use LruCache for data caching to optimize memory usage
Below 10 MB approach would increase app installs in crowded markets such as India, China and Russia!
Do not initialize objects that aren't necessary during launch times. Moving to singleton pattern helps
Testability: Providing login / sign-up details could very well improve depth of bot clicks
Printing logs on callbacks would make debugging easy for tests run in our platform
Avoid wake-locks in background, using Batch and schedulers APIs such as GCM, Job schedulers could reduce wake-locks
Unlock more fixes

Screen coverage

competition benchmark

This app is ranked #858 in Books & Reference

853
854
855
856
857
back-to-top