App Quality Dashboard


1.5 / 5

Chhi Score

This app is performing


Medium Risk


High Risk


Medium  Risk








  • Install time: Icon 44.25 Sec
  • Launch time: Icon 6.60 Sec
  • Application size: Icon 31.57 MB
  • Last tested on : 09/04/2017
  • Build ID
    :   v4.4.800
  • Chhi Score
    :   1.5
  • Change Rate
    :   -25 %

What to fix?

Build 4.4.300 did better in Memory . Spikes in Memory contributed to score drop by 9.68%

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

Must fix: App crashed because of 5889): FATAL EXCEPTION: main 5889): Process: PID: 5889 5889): java.lan... Users with phone manufactured by Lenovo might experience a crash on their phone!. Fix now!

3 Risk(s) are due to App PSS in Memory exceeding the threshold. See how to optimize memory and remove 3 High Risk(s).

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.

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

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

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

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

13 tests need immediate attention. View performance graph.

Utilization of CPU is close to the threshold.

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

Utilization of Memory is close to the threshold.

The app took 6.60 seconds to load on Android OS version 5.0.2. Usually anything more than 3.2 seconds results in user drops. View details

Lenovo A6000, Karbonn Titanium Machfive, YU Yuphoria has moved from Good to Medium risk due to RISK . View details

1 Risk(s) are due to App Total in Memory exceeding the threshold.

The app's CPU score has improved by 14.29%

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

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

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

Caching: Use LruCache for data caching to optimize memory usage

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

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

154.55 MB of App Dalvik utilized by activity View details

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

130 apps having similar CPU load have low Chhi Scores

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

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

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

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

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

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

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

Well done, Network consumption has come down by 94.94 % compared to build 4.4.300

The app's Network score has improved by 6.38% compared to build 4.4.300! Good job!

Screen coverage

competition benchmark

This app is ranked #374 in Weather