App Quality Dashboard

Reddit

1.7 / 5

Chhi Score

This app is performing

Poor

Memory

Medium Risk

/5

CPU

High Risk

/5

crash

Good 

/5

network

Good

/5

Competition

#

 

Category

Rank

  • Install time: Icon 14.08 Sec
  • Launch time: Icon 2.93 Sec
  • Application size: --- 5.62 MB
  • Last tested on : 20/04/2017
  • Build ID
    :   v2.4.10
  • Chhi Score
    :   1.7
  • Change Rate
    :   0%

Insights (26)

What to fix?

Fixing CPU risks could drastically improve Chhi Score. There are 18 CPU risks.
App launch time went up by 187.25% initlizate network calls after few seconds of loading the resources. View details
Your App CPU 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
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.
18 Risk(s) are due to Threads in CPU exceeding the threshold.
Utilization of CPU is close to the threshold.
The app's Memory score has improved by 4% compared to build v2.4.9! Good job!
19 tests need immediate attention. View performance graph.
The app has a high performance risk for the phone manufacturer(s) LYF, Micromax, Panasonic, Karbonn, YU, Samsung, Lenovo, Asus. Check coverage report for more details.
Fix & Optimize launch time using Flatbuffers for storage and rendering performance.
Do not initialize objects that aren't necessary during launch times. Moving to singleton pattern helps
There is high probability of identifying risks running the apps with conditions
Coverage: Android version coverage for reports will range between 5.1.1 to 7.1.2
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.
74.17 MB of App Dalvik utilized by activity com.reddit.frontpage.MainActivity. View details
435 apps having similar CPU load have low Chhi Scores
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.
Testability: Providing login / sign-up details could very well improve depth of bot clicks
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!
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
Well done, Network consumption has come down by 81.71 % compared to build v2.4.9
The app's Network score has improved by 53.33% compared to build v2.4.9! Good job!
Unlock more fixes

Screen Coverage

competition benchmark

This app is ranked #1063 in News & Magazines

1058
1059
1060
1061
1062
back-to-top