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

Karbonn Titanium Machfive crashed at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.reportInterruptAfterWait(AbstractQueuedSynchronizer.java:1991) View details

Must fix: App crashed because of FATAL EXCEPTION: RxIoScheduler-4 Process: flipboard.app PID: 12952 java.lang.InterruptedExcepti... Users with phone manufactured by Karbonn might experience a crash on their phone!. Fix now!

Oops!, The app crashed on Lenovo A6000, Karbonn Titanium Machfive & more devices. View details

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

Potential risk in CPU: Utilization has gone up by 37.5% compared to build v4.0.8

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

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

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

Lenovo A6000 crashed at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.reportInterruptAfterWait(AbstractQueuedSynchronizer.java:1991) 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.

Must fix: App crashed because of FATAL EXCEPTION: RxIoScheduler-4 Process: flipboard.app PID: 12952 java.lang.InterruptedExcepti... Users with phone manufactured by Lenovo 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

Utilization of CPU is close to the threshold.

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

Motorola Moto E (2nd gen), Lenovo A6000, Karbonn Titanium Machfive has moved from Good to Medium risk due to FAIL . View details

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

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

Consider re-merging the code from build v4.0.8, CPU score was 2.4

10 tests need immediate attention. View performance graph.

Build v4.0.8 did better in Memory . Spikes in Memory contributed to score drop by 5%

Utilization of Memory is close to the threshold.

435 apps having similar CPU load have low Chhi Scores

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

39.38 MB of App Dalvik utilized by activity flipboard.activities.AccountLoginActivity. View details

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

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.

Your average App Dalvik usage surged by 5.6%, Your memory score is 3.8

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

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

10 Tests crashed out of 25 Tests. Check where the app crashed. View details

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.

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

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

Caching: Use LruCache for data caching to optimize memory usage

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

App Quality Dashboard

Flipboard

#

---

TEST COVERAGE INDEX

Build ID

Chhi Score

Change Rate

Get app performance trends

43%

57%

Current Plan | Basic

80%

100%

26.4%

9.4%

20%

25%

80%

100%

26.4%

9.4%

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

923

924

925

926

927

Dive Deeper With Performance

App Speed Report

Memory Report

Network Report