App Quality Dashboard

LINE

1.9 / 5

Chhi Score

This app is performing

Average

Medium Risk

/5

High Risk

/5

Medium  Risk

/5

Good

/5

#

 

Category

Rank

  • Install time: Icon 63.79 Sec
  • Launch time: Icon 4.52 Sec
  • Application size: Icon 70.46 MB
  • Last tested on : 10/10/2017
  • Build ID
    :   v7.13.1
  • Chhi Score
    :   1.9
  • Change Rate
    :   -50 %

What to fix?

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

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.

Potential risk in CPU: Utilization has gone up by 39.29% compared to build v7.4.0

Your App CPU is now in a High Risk Zone. With a small investment into your testing you can improve your app quality better. Get more test coverage

Build v7.4.0 did better in Memory . Spikes in Memory contributed to score drop by 2.78%

Must fix: App crashed because of 961): java.lang.RuntimeException: here 961): at com.android.server.am.ActivityManagerService.... Users with phone manufactured by LYF might experience a crash on their phone!. Fix now!

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

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

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

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

19 tests need immediate attention. View performance graph.

Utilization of CPU is close to the threshold.

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

Consider re-merging the code from build v7.4.0, CPU score was 2.8

YU Yuphoria, Micromax Canvas AQ4502, LYF-WATER has moved from Good to Medium risk due to RISK . View details

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

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

40.97 MB of App Dalvik utilized by activity jp.naver.line.android.activity.registration.InputIdentifierActivity. View details

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

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

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!

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

Your average App Dalvik usage surged by 13.15%, Your memory score is 3.5

98 apps having similar CPU load have low Chhi Scores

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

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

Caching: Use LruCache for data caching to optimize memory usage

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.

The app has crashed on few device(s)! View details

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

The app's Network score has improved by 9.09% compared to build v7.4.0! Good job!

Well done, Network consumption has come down by 73.62 % compared to build v7.4.0

Screen Coverage

competition benchmark

This app is ranked #522 in Communication

517
518
519
520
521
back-to-top