App Quality Dashboard

NIV Bible

1.6 / 5

Chhi Score

This app is performing

Poor

Medium Risk

/5

High Risk

/5

Good 

/5

Medium Risk

/5

#

 

Category

Rank

  • Install time: Icon 11.44 Sec
  • Launch time: Icon 4.37 Sec
  • Application size: Icon 6.10 MB
  • Last tested on : 08/04/2017
  • Build ID
    :   v1.4
  • Chhi Score
    :   1.6
  • Change Rate
    :   -5.88 %

What to fix?

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

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

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

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.

Build v1.1 did better in Memory . Spikes in Memory contributed to score drop by 11.11%

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

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

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

App size increased by 34.07% See how to optimize.

Build v1.1 did better in Network . Spikes in Network contributed to score drop by 9.3%

25 tests need immediate attention. View performance graph.

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

Utilization of CPU is close to the threshold.

Utilization of Memory is close to the threshold.

Make sure your App's PSS isn't too high. Freeing objects that aren't needed would reduce chances of getting unexpectedly killed by Android system.

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

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

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

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!

318 apps having similar CPU load have low Chhi Scores

Your average App Dalvik usage surged by 11.64%, Your memory score is 2.4

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

49.81 MB of App Dalvik utilized by activity com.thryv.bible.activities.ReaderActivity. View details

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

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

Caching: Use LruCache for data caching to optimize memory usage

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

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

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

Screen coverage

competition benchmark

This app is ranked #1366 in Books & Reference

1361
1362
1363
1364
1365
back-to-top