Learning and careers decision
La langue française
A technical user can reproduce the core dictionary, conjugation and quiz features using supplied open data, but the full product’s editorial content, curated exercises, and site polish are not covered by a small replacement.
Visit website↗Built by Nicolas Le Roux 🇪🇺, who ships 5 products in this index
Not priced
No pricing page we fetched carried a figure, so there is nothing to compare against. The build side is still real.
$100one-off36 h to build
$0/mo3 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 searches a headword → server returns definition(s), part-of-speech, gender, examples and conjugation table; user takes short quizzes or dictées generated from entries.
What it still won’t have
- Editorial articles, ongoing content creation and curation
- A populated catalogue of quizzes, dictées and crosswords maintained by the site
- Any proprietary UX polish, analytics, and existing user accounts/subscriptions
What remains hard
- Product polish and ongoing maintenance
First-year cost
No published price
La langue française 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 French reference web app using: FastAPI (Python) backend, SQLite with FTS5, React or plain server-rendered Jinja templates, and Docker for deployment. Core features in scope: import the provided French-Dictionary CSV into SQLite; implement search-as-you-type with FTS and ranking; render word detail pages showing definitions, part-of-speech, gender, and conjugation tables (derived from CSV); generate simple weekly quizzes (10 questions) from entries and track session score locally; responsive UI, input validation, error handling, and unit tests for import, search, and quiz logic. Out of scope: editorial CMS, user accounts, paid subscriptions, large-scale analytics, and native mobile apps. Include CI (GitHub Actions) to run tests and a Dockerfile to deploy to a single small cloud VM.
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 productLa langue française — homepage
Integrity checks
What held up, and what did not.
