App Quality Dashboard

New King James Bible

1.5 / 5

Chhi Score

This app is performing


Medium Risk


High Risk










  • Install time: Icon 9.71 Sec
  • Launch time: Icon 1.38 Sec
  • Application size: Icon 6.18 MB
  • Last tested on : 15/05/2017
  • Build ID
    :   v1.4
  • Chhi Score
    :   1.5
  • Change Rate
    :   -11.76 %

What to fix?

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

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

Build v1.3 did better in Memory . Spikes in Memory contributed to score drop by 18.52%

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 25% compared to build v1.3

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

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

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

Consider re-merging the code from build v1.3, Memory score was 2.7

21 tests need immediate attention. View performance graph.

App size increased by 33.48% See how to optimize.

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

Caching: Use LruCache for data caching to optimize memory usage

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

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

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

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

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

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

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

318 apps having similar CPU load have low Chhi Scores

45.16 MB of App Dalvik utilized by activity View details

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

Your average App Dalvik usage surged by 25.76%, Your memory score is 2.2

Well done, Network consumption has come down by 37.4 % compared to build v1.3

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

Screen Coverage

competition benchmark

This app is ranked #1408 in Books & Reference