Methodology
How we build our comparisons
The sourcing rules behind every comparison on this site, so you can check the work rather than take our word for it.
Last updated September 1, 2026
The short version. Competitor facts come from that vendor's own current public pages, cited by number. When a vendor doesn't document something, we record it as not verified — never as a missing feature. We publish the categories we lose as prominently as the ones we win. Corrections go to corrections@voicecue.app and we amend the page.
Where competitor facts come from
Every competitor claim is taken from that vendor's own first-party material — product pages, pricing pages, help centres and official documentation — reviewed on September 1, 2026. We currently cite 29 linked sources. We do not source competitor capabilities from reviews, app-store descriptions written by third parties, forum posts, or AI summaries.
Every cell in the comparison carries the number of the source it came from, and the numbers are stable sitewide — source 12 is the same document on every page that cites it.
The words we use, and what they mean
Each cell gets exactly one of five statuses. The wording is fixed so that a status never quietly softens or hardens between products:
| Status | Meaning |
|---|---|
| Supported | Official evidence verifies the capability as described. |
| Limited or qualified | The capability exists, with a meaningful platform, plan, usage or implementation constraint. |
| Not verified | First-party material did not establish the claim either way. This is an absence of evidence, not evidence of absence. |
| Not available | First-party evidence, or our own audit of VoiceCue, shows the capability is absent. |
| Coming soon | Planned and announced, but not presented as a released capability. |
Each feature also carries our own editorial read of where VoiceCue stands — VoiceCue edge, broadly similar, platform-dependent, or VoiceCue gap. That label is our analysis and you should weigh it as such. The cell facts and their sources underneath it are the evidence.
How VoiceCue's own rows are audited
VoiceCue rows come from direct inspection of the live web app and the iOS and Android release-candidate builds — not from our own marketing copy. Where the web app and the mobile apps differ, the cell says so rather than quoting whichever is more flattering.
A cross-app hands-on accuracy benchmark is still pending. When it publishes it will record app version, device, operating system, script, microphone, language, network state, raw attempts and scoring rules, with uncut evidence. Until then we make no head-to-head claim about whose voice tracking is more accurate, and you should treat any such claim on this site as absent rather than implied.
Pricing
Prices are USD list prices before tax and before regional store differences. Billing periods are shown as advertised — we do not normalise annual, monthly and lifetime plans into a single like-for-like number, because they are not equivalent purchases and the arithmetic tends to flatter whoever is doing it.
What we will not do
- Turn an undocumented competitor capability into a negative claim.
- Imply affiliation with, or endorsement by, any product we compare against.
- Hide the categories where VoiceCue is behind — those rows are published in the same table, with the same prominence.
- Upgrade a claim by strengthening the adjective instead of strengthening the evidence.
- Compare against a version of a competitor's product that is no longer current.
Refresh cadence
The source audit is refreshed quarterly, and additionally after any material competitor launch or price change that we become aware of. Products in this category change quickly; if the date at the top of this page is stale, treat the comparison as stale too.
Corrections
If a claim about your product is wrong, out of date, or missing context, email corrections@voicecue.app. Point us at the first-party page that establishes the correct fact and we will amend the cell and note the change below. We would rather be corrected than be wrong.
Change history
| Date | Change |
|---|---|
| September 1, 2026 | First public revision. Initial documentation audit of seven products across sixteen features. |
Every subsequent amendment will be listed here with its date and what changed.