Can Readwise Reader be vibe coded?

Build brief — a focused alternative to Readwise Reader

**Verdict:** Partly, if you narrow it · **Buildability:** 56/100 · **Category:** Read It Later

**Source:** https://www.canitbevibecoded.com/readwise-reader

Independent editorial assessment from Can It Be Vibe Coded? Not affiliated with, endorsed by, or derived from Readwise Reader. Verify current pricing and capabilities before acting.

Context

**Readwise Reader** — Read-it-later app with highlights, RSS, PDFs, and spaced review. It currently costs $12.99/mo.

Saving articles and highlighting is easy; reliable extraction, mobile/offline reading, sync, Kindle/import integrations, RSS/PDF support, and review loops are real work.

This brief describes a focused, single-operator replacement for the part of Readwise Reader that is genuinely reproducible. It is deliberately narrower than the product it replaces, and it says so in writing. Build the useful core; do not pretend to have rebuilt the rest.

What you are building

Build a browser save endpoint, article extractor, reader view, highlights table, export to Markdown, and review emails.

Build a focused single-user workflow with real persistence, search, and export.

A responsive interface with real empty, loading, success, and error states.

Requirements

Functional

Hosted app.

Browser extension or share sheet.

Parser/extractor.

Database.

Email or notification service.

Optional OCR/PDF tools.

Non-functional

Accessibility: semantic markup, labelled controls, visible focus, and reduced-motion support.

Security: server-side secrets, validated input, and no credentials in the client bundle.

Reliability: retries with backoff on external calls, and a clear failure state when a provider is down.

Portability: the operator can export their data and leave without losing it.

Implementation brief

Build me a personal read-it-later app to replace Readwise Reader. Requirements:

A self-hosted web app (VPS or localhost): Node + Express + better-sqlite3, server-

rendered with one clean reading column.

Save via a bookmarklet POSTing the URL; extract with @mozilla/readability + jsdom and

store title, author, site, word count, and cleaned HTML. When extraction fails, keep

the bare link with a 'source only' badge instead of mangling it.

Reading view: the cleaned article, estimated read time, and select-to-highlight (a

little vanilla JS; store the highlight with surrounding context).

Library: Inbox, Archive, and per-tag lists; keyboard j/k to move, Enter to open, e to

archive.

A highlights page grouped by article, plus a nightly node-cron export of all

highlights to ~/highlights/YYYY-MM-DD.md so they outlive the app.

A daily review email with 5 random old highlights via Resend or SMTP (creds in .env).

Full-text search over articles and highlights with SQLite FTS5.

No accounts, no telemetry; if hosted, put it behind basic auth and HTTPS.

Out of scope: RSS ingestion, PDF/epub parsing, Kindle sync, and mobile apps. The

browser is the reader.

README: bookmarklet install and SMTP setup.

Delivery standard

Inspect the repository first, then write a short implementation plan before writing code.

Deliver the smallest complete end-to-end workflow first; every primary control must work against persisted data.

Use real validation and storage; never substitute fake dashboards, decorative controls, hard-coded success states, or mock integrations.

Include responsive layouts plus genuine empty, loading, success, validation, and failure states.

Keep secrets server-side in environment variables, provide .env.example, and never commit credentials or user data.

Add structured logs around every external call and return actionable errors without leaking sensitive details.

Write unit tests for the core logic and one automated test of the main user journey.

Finish with a README covering setup, architecture, data location, backups, tests, deployment, and known limitations.

Acceptance criteria

A clean install starts the app using only the README and .env.example.

The primary journey works from first visit through saved result, reload, edit, export, and deletion where applicable.

Invalid input, missing configuration, provider failure, and an empty database each have a usable state.

The interface works at 390px and 1440px, is keyboard navigable, and shows visible focus on every control.

Tests, type checking, linting, and a production build all pass with no ignored failures.

No part of the interface implies a live integration, security guarantee, or scale capability that was not actually built and verified.

Non-goals

Do not build these, and do not claim to have replaced them:

Excellent parsing.

Mobile/offline apps.

Kindle integrations.

RSS/PDF workflows.

Connectors, OAuth flows, and vendor API changes require constant upkeep.

The last 20 percent is sync, migration fidelity, speed, and edge cases.

What you still own after launch

Run migrations, backups, restores, and dependency updates.

Test the critical journey after every model, API, or hosting change.

Monitor failures and fix the edge cases a first prompt will miss.

Maintain every third-party integration as APIs and OAuth rules change.

Risk

**Operational risk.** The code is achievable; dependable data, integrations, and ongoing operations are the real cost.

Editorial confidence in this assessment: high. No independent one-shot implementation is linked yet.

Prior art

Working open-source software you can read, fork, or borrow from before starting:

[wallabag](https://github.com/wallabag/wallabag) — Open-source read-it-later app with article extraction and self-hosted reading workflows

Generated by [Can It Be Vibe Coded?](https://www.canitbevibecoded.com) · Full report: https://www.canitbevibecoded.com/readwise-reader