Must fix: App crashed because of FATAL EXCEPTION: Thread-8155 Process: com.nbcuni.telemundo.noticiastelemundo PID: 27821 java.la... Users with phone manufactured by Lava 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 9 CPU risks.

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

Potential risk in Memory: Utilization has gone up by73.68% compared to build 1.5.2-Live

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.

Your App Memory 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

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

Potential risk in CPU: Utilization has gone up by 20% compared to build 1.5.2-Live

Build 1.5.2-Live did better in Network . Spikes in Network contributed to score drop by 21.28%

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

Utilization of CPU is close to the threshold.

Lenovo A6000, Lava Iris X8, Karbonn Titanium Machfive has moved from Good to Medium risk due to RISK . View details

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

9 tests need immediate attention. View performance graph.

Consider re-merging the code from build 1.5.2-Live, Memory score was 1.9

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

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

42.00 MB of App Dalvik utilized by activity 6713. View details

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

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

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

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

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

Your average App Dalvik usage surged by 2.14%, Your memory score is 0.5

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

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

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

Caching: Use LruCache for data caching to optimize memory usage

435 apps having similar CPU load have low Chhi Scores

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

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

App Quality Dashboard

Noticias

#

---

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

1406

1407

1408

1409

1410

Test Flows	YU Yuphoria	Lava Iris X8	Karbonn Titanium Machfive	Lenovo A6000
Install app	Risk	Crash	Risk	Risk
Scenario 1	Risk	Risk
Scenario 2	Risk	Risk	Risk	Risk