App Quality Dashboard


1.1 / 5

Chhi Score

This app is performing


Medium Risk


High Risk










  • Install time: Icon 15.88 Sec
  • Launch time: Icon 1.75 Sec
  • Application size: Icon 8.75 MB
  • Last tested on : 16/03/2017
  • Build ID
    :   v5.10.6
  • Chhi Score
    :   1.1
  • Change Rate
    :   -71.79 %

What to fix?

Build 5.10.5 did better in Memory . Spikes in Memory contributed to score drop by 17.5%

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

17 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.

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 47.37% compared to build 5.10.5

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

17 tests need immediate attention. View performance graph.

Consider re-merging the code from build 5.10.5, CPU score was 1.9

Build 5.10.5 did better in Network . Spikes in Network contributed to score drop by 2.04%

Consider re-merging the code from build 5.10.5, Memory score was 4.0

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

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

70.35 MB of App Dalvik utilized by activity com.zumobi.msnbc.activities.NewsTabbedActivity. View details

Your average App Dalvik usage surged by 59.94%, Your memory score is 3.3

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

435 apps having similar CPU load have low Chhi Scores

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

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

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

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

Caching: Use LruCache for data caching to optimize memory usage

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

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

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

Screen Coverage

competition benchmark

This app is ranked #1303 in News & Magazines