Scoring rules
How we rank Bible apps
Every score starts with the same eight criteria. We separate facts found in public records from observations that would require a device test.
The short version
Each criterion receives a raw score from zero to ten. We convert that result to the published weight, add the eight weighted values and round once at the end. An unknown feature cannot receive full credit. A store rating never becomes our editorial score.
The current edition uses source records checked on . Product websites, store listings, support pages and release notes can prove that a feature exists. They cannot prove that the feature works well. We say "documented" when that boundary matters.
The 100-point scorecard
| Criterion | Weight | What we record |
|---|---|---|
| Reading experience and translation access | 15 points | Text choice, search, comparison tools, typography and reading controls. |
| Cross-platform coverage and sync | 15 points | Verified native platforms, account options and documented data that moves between devices. |
| Study tools, search and notes | 15 points | Commentaries, original-language aids, references, notes, highlights and retrieval. |
| Offline text and audio | 15 points | What remains available without a connection, separated by text, media, plans and notes. |
| AI usefulness, citations and safeguards | 10 points | Source visibility, scope, connection needs and stated safeguards. |
| Reading plans, habits and community | 10 points | Plan choice, reminders, progress, groups and sharing controls. |
| Usability and accessibility | 10 points | Interface clarity plus documented support for text sizing, screen readers and low-distraction use. |
| Price, privacy, support and updates | 10 points | Real purchase model, developer disclosures, support routes and recent maintenance. |
Published score = the sum of each raw score multiplied by its criterion weight, divided by ten.
What counts as evidence?
We keep a dated source record for every claim that could change. The strongest product records are the publisher's store listing, official documentation, current pricing page and release history. A marketing page can establish a stated feature, but it receives a clear publisher-source label.
- Confirmed platform: a current store page, official download or platform-specific support record exists.
- Publisher claim: the developer states the feature, but a second durable record was not found.
- Unknown: the available material does not answer the question.
- Not documented: we searched the relevant records and found no current claim.
We do not treat app-store privacy labels as independent audits. Apple and Google publish developer-provided declarations. When those declarations conflict, the review shows the conflict.
Documentation is not a hands-on test
A listing may say that audio downloads work offline. That record supports availability, not speed, voice quality or reliability. Claims such as "fastest search," "most accurate AI" or "best narration" require a saved test plan, named devices, app versions and results. We do not publish those claims without that record.
Our launch edition is a documentary comparison. It measures breadth, access and stated capabilities. Its original value comes from a common scoring matrix, a cross-platform map and an evidence register that makes uncertainty visible.
Publisher relationship
Best Bible App is published by Liftoff, the publisher of Bible Expert. Bible Expert still follows the same scorecard. Its source gaps, privacy-label conflicts and platform uncertainties remain visible. Competing products receive direct links to their own sites and stores.
The relationship matters because Bible Expert ranks first in the current table. Readers can inspect every criterion, compare category winners and report a factual error through the contact page.
How a score changes
We revisit prices, supported systems, feature scope and store disclosures when a material release appears. A score can rise when a missing capability gains a durable source. It can fall when an app removes support, narrows free access or leaves a product unmaintained.
- Record the new official source and retrieval date.
- Identify the affected subcriterion before changing a number.
- Recalculate from the stored raw values.
- Add a short reason to the app's score history.
- Update comparisons that rely on the changed fact.
We correct clear factual errors as soon as the replacement source is verified. Editorial disagreements do not alter a score unless they expose a problem in the stated rules.