App Quality Dashboard

feedly

2.5 / 5

Chhi Score

This app is performing

Average

Medium Risk

/5

Medium Risk

/5

Good 

/5

Good

/5

#

 

Category

Rank

  • Install time: Icon 22.38 Sec
  • Launch time: Icon 1.19 Sec
  • Application size: --- 15.66 MB
  • Last tested on : 31/05/2017
  • Build ID
    :   v37.2.0
  • Chhi Score
    :   2.5
  • Change Rate
    :   +13.64 %

What to fix?

Build v37.1.0 did better in CPU . Spikes in CPU contributed to score drop by 30.56%

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.

7 Risk(s) are due to App PSS in Memory exceeding the threshold. See how to optimize memory and remove 7 High Risk(s).

7 tests need immediate attention. View performance graph.

Consider re-merging the code from build v37.1.0, CPU score was 3.6

Utilization of Memory is close to the threshold.

The app's Memory score has improved by 9.52% compared to build v37.1.0! Good job!

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.

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

Build v37.1.0 did better in Network . Spikes in Network contributed to score drop by 2.08%

Caching: Use LruCache for data caching to optimize memory usage

Follow simple UI hierarchy by reducing nested layouts to Relative layouts.

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

Below 10 MB approach would increase app installs in crowded markets such as India, China and Russia!

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

Testability: Providing login / sign-up details could very well improve depth of bot clicks

21.85 MB of App Dalvik utilized by activity com.devhd.feedly.Main. View details

Do not initialize objects that aren't necessary during launch times. Moving to singleton pattern helps

Optimize the app to render elements at 60 FPS for buttery smooth experience.

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

Avoid wake-locks in background, using Batch and schedulers APIs such as GCM, Job schedulers could reduce wake-locks

Fix & Optimize launch time using Flatbuffers for storage and rendering performance.

Screen coverage

competition benchmark

This app is ranked #630 in News & Magazines

625
626
627
628
629
back-to-top