App Quality Dashboard

Reuters

0.9 / 5

Chhi Score

This app is performing

Poor

Medium Risk

/5

High Risk

/5

Good 

/5

Medium Risk

/5

#

 

Category

Rank

  • Install time: Icon 14.00 Sec
  • Launch time: Icon 0.00 Sec
  • Application size: Icon 8.86 MB
  • Last tested on : 03/04/2017
  • Build ID
    :   v3.2.0
  • Chhi Score
    :   0.9
  • Change Rate
    :   -52.63 %

What to fix?

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

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 v3.1.0 did better in Memory . Spikes in Memory contributed to score drop by 13.33%

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

Potential risk in CPU: Utilization has gone up by 33.33% compared to build v3.1.0

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

Build v3.1.0 did better in Network . Spikes in Network contributed to score drop by 14.29%

Consider re-merging the code from build v3.1.0, Network score was 3.5

Consider re-merging the code from build v3.1.0, CPU score was 1.5

Utilization of Network is close to the threshold.

App size increased by 31.45% See how to optimize.

The app has a high performance risk for the phone manufacturer(s) Panasonic. Check coverage report for more details.

3 tests need immediate attention. View performance graph.

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

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

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

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

Your average App Dalvik usage surged by 14.39%, Your memory score is 2.6

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

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

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

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

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

Caching: Use LruCache for data caching to optimize memory usage

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

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

38.01 MB of App Dalvik utilized by activity com.thomsonreuters.reuters.activities.HomepageActivity. View details

435 apps having similar CPU load have low Chhi Scores

Screen Coverage

competition benchmark

This app is ranked #1327 in News & Magazines

1322
1323
1324
1325
1326
back-to-top