Learning and careers decision
Plume - Word of the day
A single competent developer can reproduce the core daily-word app (local corpus, TTS audio, quizzes, progress) in a few months; what’s hard to replace are the vendor’s curated content, polished audio assets, and existing user base.
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-off120 h to build
$0/mo3 h/mo upkeep
No published price to break even against.
Open-source builds that already do this
Every project below is open source and already does this job today. Fork one, self-host it, or take the parts you need - the build prompt further down assumes an empty file, and this is the shortcut past that. Licences differ; check the one on each card before you ship. All Plume - Word of the day alternatives, with the arithmetic →
What a replacement has to do
- User opens app → app shows a single curated daily word (definition, example sentences, pronunciation) → user can heart/save, take a short practice quiz, and view progress/stats — repeat daily.
What it still won’t have
- Curated, polished editorial corpus and linguistic judgment that the original app ships
- Professional studio-recorded voice assets if the vendor uses them (unless you license or create equivalents)
- The app store listing, reviews, and existing user base
- Polish in UI/typography and ongoing product design
What remains hard
- Product polish and ongoing maintenance
First-year cost
No published price
Plume - Word of the day 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 cross-platform mobile 'word-a-day' app using React Native (Expo or bare RN), SQLite (react-native-sqlite-storage) for local corpus storage, and iOS/macOS/Android system TTS for audio. In scope: (1) ship a bundled corpus JSON -> load into SQLite with metadata (definitions, examples, etymology, Chinese glosses), (2) home screen that displays one curated daily word with pronunciation playback and voice selection, (3) save/heart words into a Vocabulary Journal with search and CSV export, (4) simple practice quiz flow and progress heatmap/stats, (5) in-app purchase flow using StoreKit/Play Billing to unlock Pro features, (6) widget support (iOS) showing the daily word, (7) offline-first behavior and local caching of audio. Out of scope: multi-language professional voice recordings (use system TTS), large-scale analytics pipeline, server-side user accounts, and app-store submission tasks. Include error handling for DB failures, audio playback failures, and purchase errors; include unit tests for the quiz engine and integration tests for DB read/write and purchase restore flows.
How we checked
How the score was reached
- Build verdict base78
- An open-source build was found+5
- 3 cited sources+3
- Evidence score86
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 · 3
Every page the run actually retrieved.
- official productPlume - Word Of The Day — App Store
- open sourceankitects/anki
- open sourcest3v3nmw/obsidian-spaced-repetition
Integrity checks
What held up, and what did not.