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.

Build 7.2.2.135 did better in Memory . Spikes in Memory contributed to score drop by 28.13%

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

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

Potential risk in CPU: Utilization has gone up by 9.09% compared to build 7.2.2.135

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

3 Risk(s) are due to Data Sent/Received in Network exceeding the threshold.

Build 7.2.2.135 did better in Network . Spikes in Network contributed to score drop by 24.39%

Fixing Network risks could drastically improve Chhi Score. There are 3 Network risks.

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

Consider re-merging the code from build 7.2.2.135, Memory score was 3.2

11 tests need immediate attention. View performance graph.

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

Consider re-merging the code from build 7.2.2.135, Network score was 4.1

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

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

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

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

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

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

Caching: Use LruCache for data caching to optimize memory usage

54.23 MB of App Dalvik utilized by activity com.viamichelin.android.viamichelinmobile.activities.CopyrightActivity. View details

120 apps having similar CPU load have low Chhi Scores

Total Network data consumed was 1160.26KB in Karbonn Titanium Machfive , This indicates the app will take 10-15 seconds on 2G network and 8-9 seconds on 3G network to load! View details

Network utilization on YU Yuphoria exceeded 1024 KB, you might want to consider bringing it down

Your average App Dalvik usage surged by 23.26%, Your memory score is 2.3

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

App makes 1160.26 KB of network requests. Moving this to a background thread will improve load speed. View details

Network utilization on Karbonn Titanium Machfive exceeded 1024 KB, you might want to consider bringing it down

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.

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

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

App Quality Dashboard

ViaMichelin

#

---

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

479

480

481

482

483

Test Flows	YU Yuphoria	Karbonn Titanium Machfive	Micromax Canvas A1	Lenovo VIBE K4 Note	Lenovo A6000
Install app	Risk	Risk	Risk	Risk	Risk
Scenario 1					Risk
Scenario 2	Risk	Risk	Risk	Risk	Risk