App Quality Dashboard

Bible

1.1 / 5

Chhi Score

This app is performing

Poor

Medium Risk

/5

High Risk

/5

Good 

/5

Medium Risk

/5

#

 

Category

Rank

  • Install time: Icon 23.89 Sec
  • Launch time: Icon 13.77 Sec
  • Application size: Icon 11.75 MB
  • Last tested on : 09/05/2017
  • Build ID
    :   v1.7.5
  • Chhi Score
    :   1.1
  • Change Rate
    :   0%

What to fix?

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

Build v1.7.1 did better in Memory . Spikes in Memory contributed to score drop by 2.94%

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 CPU risks could drastically improve Chhi Score. There are 19 CPU risks.

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

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

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

19 tests need immediate attention. View performance graph.

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

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

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

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

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

318 apps having similar CPU load have low Chhi Scores

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

62.73 MB of App Dalvik utilized by activity com.meevii.bibleverse.home.view.MainActivity. 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!

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

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

Caching: Use LruCache for data caching to optimize memory usage

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

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

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

Network utilization on Motorola Moto E (2nd gen) 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

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

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

Well done, Network consumption has come down by 80.48 % compared to build v1.7.1

competition benchmark

This app is ranked #1537 in Books & Reference

1532
1533
1534
1535
1536
back-to-top