App Quality Dashboard

Italiano

3.4 / 5

Chhi Score

This app is performing

Average

Medium Risk

/5

Medium Risk

/5

Good 

/5

Good

/5

#

 

Category

Rank

  • Install time: Icon 5.36 Sec
  • Launch time: Icon 1.11 Sec
  • Application size: Icon 6.49 MB
  • Last tested on : 25/03/2017
  • Build ID
    :   v3.5
  • Chhi Score
    :   3.4
  • Change Rate
    :   -17.07 %

What to fix?

Build 3.4 did better in Memory . Spikes in Memory contributed to score drop by 19.51%

Build 3.4 did better in CPU . Spikes in CPU contributed to score drop by 29.27%

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.

Consider re-merging the code from build 3.4, Memory score was 4.1

Consider re-merging the code from build 3.4, CPU score was 4.1

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

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

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

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

43.81 MB of App Dalvik utilized by activity livio.pack.lang.it_IT.DictionaryView. View details

Upload APKs with and without 3rd Party SDKs to monitor and optimize the impact of app performance

Your average App Dalvik usage surged by 0.44%, Your memory score is 3.3

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

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

Fix Oncreate() if the launch time is exceeding more than 3.2 secs. Try deflating views and layouts to optimize.

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

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

Printing logs on callbacks would make debugging easy for tests run in our platform

Screen Coverage

competition benchmark

This app is ranked #509 in Books & Reference

504
505
506
507
508
back-to-top