App Quality Dashboard


0.3 / 5

Chhi Score

This app is performing


High Risk


Medium Risk




Medium Risk






  • Install time: Icon 15.67 Sec
  • Launch time: Icon 2.45 Sec
  • Application size: Icon 4.42 MB
  • Last tested on : 06/03/2017
  • Build ID
    :   v2.1.0
  • Chhi Score
    :   0.3
  • Change Rate
    :   -92.31 %

What to fix?

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

Build v1.2 did better in CPU . Spikes in CPU contributed to score drop by 8.33%

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

Potential risk in Memory: Utilization has gone up by86.49% compared to build v1.2

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 34.62% initlizate network calls after few seconds of loading the resources. View details

18 tests need immediate attention. View performance graph.

Consider re-merging the code from build v1.2, Memory score was 3.7

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

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

Utilization of CPU is close to the threshold.

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

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

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

59.00 MB of App Dalvik utilized by activity 1279. View details

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

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

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

Caching: Use LruCache for data caching to optimize memory usage

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!

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

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

The app's Network score has improved by 14.29% compared to build v1.2! Good job!

Well done, Network consumption has come down by 81.26 % compared to build v1.2

competition benchmark

This app is ranked #3455 in Lifestyle