App Quality Dashboard


1.6 / 5

Chhi Score

This app is performing


Medium Risk


High Risk




High Risk






  • Install time: Icon 7.33 Sec
  • Launch time: Icon 2.36 Sec
  • Application size: Icon 3.04 MB
  • Last tested on : 16/05/2017
  • Build ID
    :   v0.0.10
  • Chhi Score
    :   1.6
  • Change Rate
    :   -5.88 %

What to fix?

Potential risk in Network: Utilization has gone up by69.23% compared to build v0.0.9

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

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

Build v0.0.9 did better in Memory . Spikes in Memory contributed to score drop by 11.54%

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

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

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

3 Risk(s) are due to Data Sent/Received in Network exceeding the threshold.

9 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) LYF, Lenovo. Check coverage report for more details.

The app's CPU score has improved by 14.29%

Consider re-merging the code from build v0.0.9, Network score was 3.9

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

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

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

Your average App Dalvik usage surged by 15.61%, Your memory score is 2.3

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

Network utilization on Lenovo A6000 exceeded 1024 KB, you might want to consider bringing it down

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

29.82 MB of App Dalvik utilized by activity com.islet.chitkalu.MainActivity. View details

App makes 2969.16 KB of network requests. Moving this to a background thread will improve load speed. View details

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

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

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

Total Network data consumed was 2969.16KB in Lenovo A6000 , This indicates the app will take 10-15 seconds on 2G network and 8-9 seconds on 3G network to load! View details

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

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

574 apps having similar CPU load have low Chhi Scores

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

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

Screen Coverage

competition benchmark

This app is ranked #2931 in Lifestyle