App Quality Dashboard

Korean

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 23.31 Sec
  • Launch time: Icon 1.38 Sec
  • Application size: --- 17.60 MB
  • Last tested on : 26/04/2017
  • Build ID
    :   v11.3.0
  • Chhi Score
    :   2.8
  • Change Rate
    :   -12.5 %

What to fix?

Build v11.2.0 did better in Memory . Spikes in Memory contributed to score drop by 12.9%

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

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

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

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.

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

Utilization of CPU is close to the threshold.

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

21 tests need immediate attention. View performance graph.

Build v11.2.0 did better in Network . Spikes in Network contributed to score drop by 4.08%

84.00 MB of App Dalvik utilized by activity 62. View details

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

Your average App Dalvik usage surged by 41.59%, Your memory score is 2.7

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

Caching: Use LruCache for data caching to optimize memory usage

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

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

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

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

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

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

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

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

Screen Coverage

competition benchmark

This app is ranked #892 in Books & Reference

887
888
889
890
891
back-to-top