Must fix: App crashed because of FATAL EXCEPTION: main Process: com.reddys.mansuitphotonew PID: 19712 java.lang.NullPointerExcep... Users with phone manufactured by Motorola might experience a crash on their phone!. Fix now!

Potential risk in CPU: Utilization has gone up by 25% compared to build v2.24

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 15 CPU risks.

Must fix: App crashed because of FATAL EXCEPTION: main Process: com.reddys.mansuitphotonew PID: 19712 java.lang.NullPointerExcep... Users with phone manufactured by LYF might experience a crash on their phone!. Fix now!

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

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

Build v2.24 did better in Memory . Spikes in Memory contributed to score drop by 6.67%

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) Karbonn, Micromax, Asus, Panasonic, LYF, YU, Motorola. Check coverage report for more details.

9 tests need immediate attention. View performance graph.

The app's memory score is 2.8 due to high memory utilization. Needs to be fixed as priority.

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

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.

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

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

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

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

Your average App Dalvik usage surged by 0.95%, Your memory score is 2.8

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

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

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

Caching: Use LruCache for data caching to optimize memory usage

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.

358 apps having similar CPU load have low Chhi Scores

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

53.88 MB of App Dalvik utilized by activity com.startapp.android.publish.adsCommon.activities.OverlayActivity. View details

Motorola Moto E (2nd gen) health improved from Medium risk to Good eliminating FAIL

LYF health improved from Medium risk to Good eliminating FAIL

Panasonic P55 health improved from Medium risk to Good eliminating FAIL

Zenfone 2 Laser health improved from Medium risk to Good eliminating FAIL

Test Flows	YU Yuphoria	Panasonic P55	LYF	Karbonn Titanium Machfive	Zenfone 2 Laser	Micromax Canvas A1	Motorola Moto E (2nd gen)
Install app	Risk	Risk	Crash	Risk	Risk	Risk	Crash
Scenario 1	Risk	Risk	Failure	Risk	Failure	Risk	Failure
Scenario 2		Failure			Failure		Failure

App Quality Dashboard

Man Suit

#

---

TEST COVERAGE INDEX

Build ID

Chhi Score

Change Rate

Get app performance trends

0

0

0

0

Functional Test Coverage

Run tests in

Run tests with

competition benchmark

911

912

913

914

915