Learning and careers decision
divinetalk
A capable engineer can build a useful conversational Bible-and-devotional replacement using open Bible projects and an LLM, but reproducing the polished app-store product, subscription polish, and community features would take substantially more effort and product work than a minimal replacement.
View on the App Store↗Not priced
No pricing page we fetched carried a figure, so there is nothing to compare against. The build side is still real.
$100one-off70 h to build
$50/mo6 h/mo upkeep
No published price to break even against.
No open-source build does this yet
Nothing published replaces this one, so a replacement starts from an empty file. Here is what it would have to cover.
What a replacement has to do
- User asks a question or opens a devotional → backend looks up matching scripture passages → LLM crafts a Scripture-grounded response (or templates one) → app displays response and optional shareable verse image; daily devotional delivered by scheduled job.
What it still won’t have
- Polished App Store presence and design polish from a professional mobile studio
- Proprietary editorial content, curated reading plans and exclusive features mentioned in app updates
- Existing user reviews/ratings and any community features (community prayer feed)
- Paid-subscription billing, analytics and A/B experimentation infrastructure
What remains hard
- Product polish and ongoing maintenance
First-year cost
No published price
divinetalk does not publish a price we could read, so there is nothing to compare against. What building costs is below.
Money you would actually spend
Time you would spend
—
What you would spend
What we assumed
The verdict above measures whether you could build it. This one is only about money.
Runnable build prompt
Build a minimal DivineTalk replacement using React Native for mobile, Node.js + Express for the API, Postgres for scripture storage, and OpenAI (or equivalent) for responses. In scope: 1) iOS/Android app with screens for asking a question, viewing an LLM-generated Scripture-grounded answer, a daily devotional page, and a shareable verse-image composer; 2) backend endpoints to accept prompts, lookup scripture passages (search by keyword/verse id), call the LLM with prompt templates that include matched verses, and return structured responses; 3) scripture ingestion script to import public-domain Bible texts into Postgres and full-text search via Postgres tsvector; 4) scheduled job (cron) to create and push daily devotionals; 5) simple user auth (email) and a stubbed subscription flag (no payment gateway integration required); 6) server-side PNG renderer for verse images (e.g., headless Chromium or node-canvas). Out of scope: community prayer feed, mature payment processing, analytics dashboards, multi-language localization beyond English. Require input validation, error handling on all network and API calls, unit tests for backend logic, and end-to-end smoke tests for core flows.
How we checked
How the score was reached
- Partly verdict base52
- Evidence score52
The base comes from the verdict. Everything under it is a check that either happened or did not, and each one is a fact frozen in this record rather than a judgement made at render time - so the same evidence always produces the same number.
How scoring works →Cited sources · 1
Every page the run actually retrieved.
- official productDivineTalk - Bible Tracker - App Store
Integrity checks
What held up, and what did not.
