App Quality Dashboard

Por-Eng Dictionary +

1.6 / 5

Chhi Score

This app is performing

Poor

Medium Risk

/5

Medium Risk

/5

Good 

/5

Good

/5

#

 

Category

Rank

  • Install time: Icon 17.89 Sec
  • Launch time: Icon 6.00 Sec
  • Application size: Icon 9.01 MB
  • Last tested on : 27/04/2017
  • Build ID
    :   v7.1.29
  • Chhi Score
    :   1.6
  • Change Rate
    :   -51.52 %

What to fix?

App launch time went up by INF% initlizate network calls after few seconds of loading the resources. View details

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 18 CPU risks.

18 Risk(s) are due to Threads in CPU exceeding the threshold.

Build v6.4.14 did better in CPU . Spikes in CPU contributed to score drop by 21.74%

Build v6.4.14 did better in Memory . Spikes in Memory contributed to score drop by 22.58%

19 tests need immediate attention. View performance graph.

App size increased by 11.65% See how to optimize.

The app has a high performance risk for the phone manufacturer(s) OnePlus, Spice, Motorola, Karbonn, Coolpad, Samsung, YU. Check coverage report for more details.

Consider re-merging the code from build v6.4.14, Memory score was 3.1

The app took 6.00 seconds to load on Android OS version 6.0. Usually anything more than 3.2 seconds results in user drops. View details

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

63.10 MB of App Dalvik utilized by activity com.ascendo.android.dictionary.activities.LookupWordScreen. View details

Your average App Dalvik usage surged by 42%, Your memory score is 2.4

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

Caching: Use LruCache for data caching to optimize memory usage

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.

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

There is high probability of identifying risks running the apps with conditions

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

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

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

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

Well done, Network consumption has come down by 15.27 % compared to build v6.4.14

The app's Network score has improved by 2.33% compared to build v6.4.14! Good job!

Screen Coverage

competition benchmark

This app is ranked #2128 in Education

2123
2124
2125
2126
2127
back-to-top