App Quality Dashboard


2.2 / 5

Chhi Score

This app is performing


Medium Risk


High Risk










  • Install time: Icon 17.89 Sec
  • Launch time: Icon 0.97 Sec
  • Application size: Icon 6.52 MB
  • Last tested on : 26/04/2017
  • Build ID
    :   v1.7.10
  • Chhi Score
    :   2.2
  • Change Rate
    :   -43.59 %

What to fix?

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

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.

Potential risk in CPU: Utilization has gone up by 26.09% compared to build v1.7.9

8 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

Build v1.7.9 did better in Network . Spikes in Network contributed to score drop by 10.87%

8 tests need immediate attention. View performance graph.

Consider re-merging the code from build v1.7.9, CPU score was 2.3

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

Build v1.7.9 did better in Memory . Spikes in Memory contributed to score drop by 7.69%

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

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

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

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

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

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

Caching: Use LruCache for data caching to optimize memory usage

81 apps having similar CPU load have low Chhi Scores

62.72 MB of App Dalvik utilized by activity View details

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

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

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

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

Your average App Dalvik usage surged by 34.16%, Your memory score is 3.6

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.

competition benchmark

This app is ranked #297 in Food & Drink