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

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

5 Risk(s) are due to App PSS in Memory exceeding the threshold. See how to optimize memory and remove 5 High Risk(s).

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

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!

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

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

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

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.

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

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

YU Yuphoria, Micromax Canvas AQ4502, LYF-WATER has moved from Good to Medium risk due to RISK . 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

Utilization of CPU is close to the threshold.

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

19 tests need immediate attention. View performance graph.

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

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

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

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

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

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

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

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

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!

98 apps having similar CPU load have low Chhi Scores

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

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

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

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

Caching: Use LruCache for data caching to optimize memory usage

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

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

Test Flows	YU Yuphoria	LYF-WATER	Karbonn Titanium Machfive	Micromax Canvas AQ4502	Micromax Canvas Xpress	Lenovo A6000	Samsung Duos Galaxy J7
Install app	Risk	Risk	Success	Risk	Success	Success	Success
Scenario 1	Success	Risk	Success	Risk	Risk	Success	Success
Scenario 2	Success	Risk	Risk	Risk	Success	Risk	Risk
Scenario 3	Risk	Risk	Risk	Risk	Risk	Success	Risk
Scenario 4	Success	Crash	Risk	Risk	Success	Success	Success

App Quality Dashboard

LINE

#

---

TEST COVERAGE INDEX

Build ID

Chhi Score

Change Rate

Get app performance trends

50%

50%

Current Plan | Basic

100%

100%

38.4%

14.8%

20%

25%

100%

100%

38.4%

14.8%

20%

25%

Network on 3G

13.1%

13.1%

13.1%

13.1%

45.1%

15.1%

14.1%

13.1%

By RAM

By Version

By Display

0

0

0

0

Functional Test Coverage

Run tests in

Run tests with

competition benchmark

517

518

519

520

521

Dive Deeper With Performance

App Speed Report

Memory Report

Network Report