- Starting price
- Free
- Free tier
- Yes
- Platforms
- iPhone · iPad · Android · Apple silicon Mac
- Developer
- Frontier R&D / Ryder Wishart
- Launched
- 2025
- Updated
- Aug 16, 2026
The verdict
LangQuest addresses a real field constraint: translation work cannot wait for a stable connection, a laptop, or a writing system. Its short-task structure, audio capture, local storage, community voting, manual backup, and free access are promising for supervised language-documentation and oral Scripture projects. The defining trade-off is permanent openness: translations, recordings, comments, and votes are dedicated to CC0 for anyone to reuse without attribution, including in AI. Secure informed community consent, define review authority and sensitivity rules, test offline recovery, and export a project copy before collecting irreplaceable voices.
Try LangQuest ↗Opens langquest.org
LangQuest is a free mobile application from Canadian research-and-development company Frontier R&D. It is designed to collect translation and language material where connectivity may disappear for weeks or months and where audio can be more useful than text. A project can be divided into quests and smaller assets; contributors translate Scripture, stories, songs, educational material, or cultural knowledge with voice, text, and images; other participants comment and vote; and validated material can become an open language dataset. The Christian use case is explicit—its store description says the product grew from the need to capture oral Bible translation—but the tool is not limited to Scripture.
The app’s most important promise is offline-first work. Apple’s listing says projects and recordings remain local while disconnected and synchronize after connectivity returns. Recent versions added manual backup of local-only recordings and text, audio export, verse labeling, multiple versions of a pericope or chapter, invitation improvements, transcription, and a growing localization set. That is stronger than a web form with an offline cache, but “offline-first” still needs a field test on the exact phones, storage limits, operating-system versions, project sizes, authentication state, and multi-contributor handoff pattern a team will use.
LangQuest makes an unusually broad data bargain. Its terms say every contributed translation, recording, comment, and vote is placed under CC0 1.0, waiving copyright and related rights to the extent legally possible. The dedication cannot be revoked after submission, survives account termination, permits commercial reuse, requires no attribution, and is intended to support public resources and AI models. That can be excellent infrastructure for low-resource languages. It can also conflict with community protocols, speaker expectations, sacred or restricted material, contributor-credit norms, Indigenous data sovereignty, child protection, or a source text whose license does not permit republication.
This is a researched review based on the official site, current policies, exact Apple and Google records, release history, and public GitHub repository. We did not create a production project, record a speaker, remain offline for months, provoke sync conflicts, inspect a published dataset, evaluate AI suggestions, verify voting quality, request account deletion, or audit application security. The public repository was active on the date checked, with 15 stars, 12 listed contributors, and no GitHub-detected license file even though the website and terms describe the source as MIT. Capability and license statements therefore remain vendor claims where direct evidence does not close the gap.
✓ The good
- Built around field reality - text, voice, images, local storage, delayed synchronization, and manual backup support constrained environments
- Free access - no subscription or in-app purchase appears on either current store listing
- Oral-language support - contributors can capture recordings without requiring a complete orthography or fluent keyboard input
- Structured collaboration - projects, quests, assets, invitations, comments, versions, and votes make contribution roles visible
- Open-data mission is explicit - CC0 terms state exactly how validated language material may be reused
- Active development - version 2.2.4 followed frequent 2025–2026 releases and the public repository was updated when checked
- Useful recovery additions - manual backups and audio export reduce dependence on a successful future sync
- Analytics opt-out - the privacy policy documents an in-app control that disables further analytics and session replay collection
✗ Watch out
- CC0 is permanent - contributors cannot withdraw the public-domain dedication after material is submitted
- No attribution requirement - speakers, translators, communities, and funders may receive no credit from downstream users
- AI reuse is intentional - public content may train text, speech-recognition, speech-synthesis, and other models beyond the original project
- Young and lightly adopted - Apple shows no rating overview and Google Play shows only 100+ downloads
- Offline collaboration is not finished - the official site labels peer-to-peer device syncing as coming soon
- Sensitive public content risk - audio, comments, and language data can reveal identity, beliefs, location, relationships, or restricted knowledge
- US data processing - the Canadian operator says all account and service data is processed and stored in the United States
- License evidence conflicts - official terms say MIT, but GitHub did not detect a repository license file when checked
Best for
- Supervised oral Bible-translation teams with explicit authority to release recordings and text under CC0
- Language-documentation projects that value unrestricted downstream reuse more than attribution or withdrawal
- Community workshops working through long periods of unreliable internet on ordinary phones
- Projects willing to define contributor consent, review roles, source rights, and independent backup before collection
- Technical teams able to evaluate a young open-source application and contribute reproducible issue reports
Avoid if
- A speaker, community, church, publisher, or funder requires attribution, noncommercial use, access limits, or later withdrawal
- The material includes confidential testimony, endangered people, sacred restrictions, precise locations, minors, or third-party secrets
- Your source Bible, images, songs, stories, or curriculum cannot legally be placed into the public domain
- You need mature peer-to-peer collaboration with no eventual server connection
- Your organization requires a verified repository license, independent security assurance, regional hosting, or contractual support
What LangQuest is
LangQuest is a collection and coordination tool, not an automated Bible translator. Its hierarchy breaks a broad project into quests and bite-sized assets. Contributors create text or audio versions, attach media, review alternatives, comment, vote, and publish material after a project-defined validation process. Experimental AI can propose or transcribe content, but the community supplies language knowledge and bears responsibility for the final data.
It is also a data-publication system. A recording made for one translation session can become a reusable global asset under CC0. That dual identity is central: the same openness that helps researchers, educators, Bible agencies, dictionary makers, and speech-technology developers can erase the contributor’s control over context and downstream use. Teams should explain both identities before the record button is pressed.
Why offline collection and irrevocable open data belong in the same project decision
Many translation systems assume a laptop, trained specialist, mature orthography, and dependable sync. LangQuest moves contribution onto a common phone, lets a speaker answer by voice, stores work locally, and divides a large corpus into manageable tasks. That can broaden participation and keep a project moving when infrastructure fails. Votes and multiple versions can expose disagreement instead of forcing the first recording to become final.
Broader participation does not automatically create informed permission. A contributor may understand “help translate this verse” without understanding “any company may permanently reuse my voice, without credit, to train an AI model.” Explain the destination in the contributor’s language; distinguish local draft from submitted public content; record who has authority over communal material; provide a no-recording route; and decide whether names, faces, locations, comments, or raw voices should be collected at all. The data license should shape the workflow from recruitment onward.
Projects, quests, assets, and voting: structure helps only when authority is also defined
A project represents a larger goal such as a Bible book, story collection, dictionary, or course. Quests divide that goal into focused assignments, while assets hold small units of source material and one or more translated, transcribed, recorded, or image-linked contributions. Invitations bring contributors into a project. Comments, votes, multiple versions, and publication actions provide a basic route from collection through review.
The software cannot decide whose vote counts as linguistic expertise, whether consensus is theological accuracy, how dialect disagreements should be represented, or who may release a sacred text. Write those rules separately. Use role-based review, preserve minority variants where valuable, require source-reference checks, distinguish comprehension testing from popularity voting, and keep an auditable decision record. For Scripture, language naturalness, fidelity to source, community acceptance, and ecclesial authorization are related but different questions.
Offline-first audio: test loss, conflict, and recovery before the remote workshop
The stores describe local access for weeks or months, automatic later synchronization, text and voice recording, verse labels, playback, audio merging and reordering, export, and manual backup of local-only content. These are the right ingredients for hot, humid, low-bandwidth settings in which a laptop or constant server round trip is fragile. Recent release notes show repeated work on authentication, local databases, attachment queues, playback, voice detection, and offline recording.
Frequent fixes also show where field risk lives. Before deployment, load the real project size; fill storage; revoke connectivity; restart the phone; expire authentication; edit the same asset on two devices; interrupt a large upload; restore a manual backup to another device; and verify file names, metadata, order, votes, and rights state after recovery. Keep raw source recordings outside the app until a second copy is proven, and never postpone export until the only phone is about to travel.
AI, analytics, and open reuse: three different data flows need three different consents
The product site advertises AI-assisted initial translations, and release notes mention experimental transcription and smarter language suggestions. Separately, PostHog may receive device details, approximate city and country, usage paths, performance events, account-linked user ID, and limited session replay unless analytics is disabled. Separately again, contributed translations, recordings, comments, and votes become CC0 public content intended for unrestricted use and AI development.
Do not collapse these into one “technology consent.” A participant may accept local recording but decline analytics; accept community review but reject public voice release; or permit a published transcript while withholding raw audio from model training. The current terms do not offer a restricted license for submitted contributions, so material that cannot be CC0 should remain out of the service. Disable optional analytics on field devices where appropriate, avoid personal detail in comments, and obtain written answers about the AI providers and retention before using experimental features on unpublished content.
Pricing
Mobile application
Free
The Apple and Google listings show a free download without a public subscription or in-app-purchase schedule. Projects, offline work, recording, comments, voting, synchronization, backup, and publication are presented as part of the service. Confirm any practical storage, project, member, transcription, AI, or export limits with the operator before a funded deployment.
Language-data contribution
CC0 1.0 dedication
There is no cash fee, but there is a permanent rights cost. The terms require contributed translations, audio, comments, and votes to enter the worldwide public domain without attribution and say the dedication cannot be revoked. Treat consent, authority, source licensing, personal data, cultural protocol, and AI reuse as acceptance gates—not as a footer participants will read later.
Field deployment
Organization-funded
Phones, protective cases, microphones, power, travel, connectivity, facilitation, translator compensation, safeguarding, training, local backups, review, and long-term stewardship remain project costs. Free software does not make ethical collection or reliable preservation free. Budget for recovery drills and a second archive outside LangQuest.
LangQuest is free in both mobile stores, and the public product pages do not advertise a premium plan. That makes a genuine pilot accessible to small language communities and ministries.
The nonfinancial exchange is significant: submitted content enters CC0. A project does not receive exclusivity, attribution, a noncommercial limit, a ministry-only limit, or a later takedown right through that license.
AI and transcription may create separate infrastructure costs for the operator even if users are not charged today. Ask whether quotas, provider changes, grants, or future paid services could affect a multi-year project.
Budget for the human system around the app. Translation review, speaker compensation, consent, devices, power, travel, safeguarding, metadata, backups, correction, and dataset stewardship will cost more than the download.
Where LangQuest falls behind
The public contribution boundary needs a staged consent interface. Every recording and submission screen should distinguish private local draft, project-only review, validated release, public dataset, and AI reuse; show the exact license in the contributor’s language; and require affirmative authority at publication rather than burying irrevocable CC0 in general terms.
Peer-to-peer offline collaboration remains future work. Local-first storage helps one device, but a disconnected team still lacks a mature documented way to exchange and reconcile work device to device without reaching the central service. That is a meaningful limitation in the environments the product is designed to serve.
The GitHub licensing state should be repaired. The terms and site footer call the code MIT, yet the repository metadata reported no recognized license and the root did not expose a standard license through GitHub when checked. Add a canonical LICENSE file, identify third-party assets, and separate code licensing from trademarks and contributed data.
Privacy detail stops too early. The policy names PostHog and US processing but not hosting vendors, AI or transcription providers, storage regions, raw-audio retention, backup deletion, encryption scope, moderator access, abuse reporting, public-dataset removal exceptions, or a complete subprocessor list.
Public language corpora need governance beyond an acceptable-use list. Publish a protocol for child voices, biometric and re-identification risk, endangered communities, sacred or gender-restricted knowledge, disputed ownership, speaker withdrawal requests, malicious uploads, source-license complaints, dataset versions, corrections, provenance, and responsible AI access.
Adoption evidence is early. One hundred-plus Google Play downloads, no visible Apple rating summary, 15 GitHub stars, and a rapidly changing release history are appropriate for a pilot, not proof that irreplaceable field data will remain safe across years. Publish durability, recovery, sync-conflict, security, and field-evaluation results.
LangQuest vs. Paratext vs. Scripture Forge vs. Oral Collector
Paratext is the mature professional environment for Scripture translation: source-language resources, project checks, team roles, publishing preparation, and an institutional ecosystem. It is stronger for specialist exegesis and controlled translation production, but heavier to deploy and not built around anonymous unrestricted release of every contribution. LangQuest is better viewed as a mobile collection and participation layer than as a replacement for Paratext’s checking and publishing discipline.
Scripture Forge brings collaborative drafting, checking, community review, and translation suggestions into a browser-centered workflow that can connect with Paratext projects. It is closer to formal Bible-translation production, while LangQuest emphasizes field-resilient multimodal capture and CC0 publication. Oral Collector focuses on guided oral-language collection and can suit specific story or Scripture workflows. Compare the desired final license, offline duration, device pattern, review authority, source integration, data export, and whether raw voice should ever become public—not simply the number of recording buttons.
The bottom line
LangQuest is a thoughtful response to the hardest part of language technology: the data often exists only in people, far from dependable infrastructure. Free mobile access, local work, audio-first capture, small tasks, community review, manual backup, and open outputs can make a project possible. But its openness is irreversible and unusually permissive. Use it when a community knowingly wants a CC0 public corpus, not merely when a coordinator wants a convenient recorder. With explicit multilingual consent, licensed sources, defined validators, low-sensitivity metadata, independent backups, tested recovery, and a separate professional translation check, it can be a valuable field instrument.
Alternatives to LangQuest
Scripture ForgeA browser-based collaborative translation and checking workspace with community review and Paratext connections. Better aligned with controlled project production; less centered on long-disconnected mobile audio collection.Oral CollectorA mobile-oriented oral collection tool for guided recording workflows. Compare export, offline recovery, project governance, licensing, and the exact method used to turn recordings into reviewed Scripture.BloomA free tool for creating books and accessible literacy materials in local languages, including audio and picture content. Better for finished publications; not the same distributed translation-voting dataset model.Frequently asked questions
Is LangQuest free?
Yes. The current Apple App Store and Google Play listings show a free download, and the official site does not publish a paid plan or in-app-purchase schedule. Organizations still need to budget for devices, power, travel, training, contributor compensation, review, backup, and stewardship. Ask Frontier R&D about project, storage, AI, transcription, and support limits before depending on the service long term.
Does LangQuest work fully offline?
The official listings describe offline-first local work for weeks or months and later automatic sync, and recent releases added manual backup. That does not mean every account, invitation, AI, publication, conflict-resolution, or team operation works without a server. Peer-to-peer offline collaboration is explicitly marked “coming soon.” Test the exact workflow and recovery path before a remote deployment.
Who owns recordings and translations contributed to LangQuest?
The terms require translations, recordings, comments, and votes to be dedicated under CC0 1.0 Universal. That places them as fully as possible into the public domain, permits any purpose without attribution, and cannot be revoked after contribution. A project should obtain informed authority from speakers, translators, communities, and source-rights holders before submission.
Can LangQuest content be used to train AI?
Yes. The official policy expressly says the public language data is intended to support resources and AI models, including text, speech recognition, and speech synthesis. CC0 allows commercial and noncommercial AI reuse without attribution. Do not upload a voice, text, image, story, or comment unless that downstream use is acceptable and legally authorized.
Does LangQuest translate the Bible with AI?
The site advertises AI-assisted initial translations, and release notes include experimental transcription and smarter language suggestions. Those are draft aids, not a guarantee of linguistic, exegetical, theological, or cultural accuracy. Native speakers, trained translators, source-text specialists, community reviewers, and the responsible church or translation organization still need a defined validation process.
What personal data does LangQuest collect?
The policy lists an optional recovery email, username, submitted translations, recordings, comments and votes, communications, device and usage information, approximate location, performance events, identifiers, and limited session replay through PostHog. Analytics can be disabled in profile settings. The Canadian operator says data is processed and stored in the United States and the service is not directed to children under 13.
Is LangQuest open source?
Its official terms say the source is available under MIT, and development is public on GitHub. However, GitHub reported no detected repository license when we checked on August 16, 2026. Until a canonical license file clearly covers the current tree, treat the advertised MIT status as unresolved and ask the maintainers before redistributing a fork. User-contributed data follows the separate CC0 terms.
Sources & further reading
More Greek & Hebrew Tools
Codex Translation EditorA free, open-source, offline-first desktop workspace for lean and low-resource translation teams, combining structured imports, project-aware AI, backtranslation, validation, audio, collaboration, and rich exports—one of the most ambitious mission tools in this directory, but still specialist software whose AI and cloud governance require expert ownership.
Blue Letter BibleThe serious-study site for everyone who can't afford Logos - and a surprising number of people who can.
Bible HubThe most-cited free Bible study site on the internet - a thirty-translation parallel view, a Strong's-tagged interlinear, and a wall of classical commentaries on every verse, all one click apart and all completely free.
STEPBibleA free, open-source original-language Bible study site built by actual textual scholars at Tyndale House Cambridge - and the best-kept secret in serious Bible study.
BibleArcThe diagramming workbench seminarians swear by and most casual readers have never heard of - and the reason that gap exists is the same reason its fans will not give it up.
AquillaA promising web-first translation workspace that puts AI drafts, back-translations, quality checks, audio and human review in one place—free today, proven in ambitious mission projects, and still missing public legal and security detail that serious teams need.