App Quality Dashboard

Japanese

2.8 / 5

Chhi Score

This app is performing

Average

Medium Risk

/5

Medium Risk

/5

Good 

/5

Good

/5

#

 

Category

Rank

  • Install time: Icon 24.50 Sec
  • Launch time: Icon 2.73 Sec
  • Application size: --- 24.89 MB
  • Last tested on : 26/04/2017
  • Build ID
    :   v11.3.0
  • Chhi Score
    :   2.8
  • Change Rate
    :   +75 %

What to fix?

15 Risk(s) are due to App PSS in Memory exceeding the threshold. See how to optimize memory and remove 15 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.

Fixing CPU risks could drastically improve Chhi Score. There are 9 CPU risks.

Build v11.2.0 did better in CPU . Spikes in CPU contributed to score drop by 16.67%

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

9 Risk(s) are due to CPU Load in CPU exceeding the threshold.

18 tests need immediate attention. View performance graph.

Utilization of CPU is close to the threshold.

Consider re-merging the code from build v11.2.0, CPU score was 3.6

Utilization of Memory is close to the threshold.

8 Risk(s) are due to App Total in Memory exceeding the threshold.

The app's Memory score has improved by 42.11% compared to build v11.2.0! Good job!

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

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

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

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

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

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

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

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

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

80.30 MB of App Dalvik utilized by activity com.bravolang.japanese.LanguageSetting. View details

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

Caching: Use LruCache for data caching to optimize memory usage

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!

Samsung Galaxy J7 health improved from High risk to Good eliminating CRASH

Screen coverage

competition benchmark

This app is ranked #894 in Books & Reference

889
890
891
892
893
back-to-top