App Quality Dashboard

Amplified Bible

1.7 / 5

Chhi Score

This app is performing

Poor

Medium Risk

/5

Medium Risk

/5

Good 

/5

Good

/5

#

 

Category

Rank

  • Install time: Icon 11.08 Sec
  • Launch time: Icon 3.36 Sec
  • Application size: Icon 6.46 MB
  • Last tested on : 15/03/2017
  • Build ID
    :   v1.4
  • Chhi Score
    :   1.7
  • Change Rate
    :   0%

What to fix?

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

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

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

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.

App size increased by 31.57% See how to optimize.

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

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

24 tests need immediate attention. View performance graph.

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

Your average App Dalvik usage surged by 5.18%, Your memory score is 2.6

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

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

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

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

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

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

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.

Caching: Use LruCache for data caching to optimize memory usage

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

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

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

competition benchmark

This app is ranked #1316 in Books & Reference

1311
1312
1313
1314
1315
back-to-top