ReadingCAN I VIBECODE
Recall?
BUILD FIRST
- One specific customer type and one primary use case
- A vertical slice that completes the main job without manual workarounds
- Visible limits, review steps, and a fallback when an external dependency fails
LEAVE FOR LATER
- Broad third-party integrations
- High-scale collaboration, syncing, and permissions
- Automation that can cause harm without human review
RESEARCH NOTES
What this tool actually does.
Recall Reader (Recall Reader Inc.) is an Android EPUB/e-book reader optimized for e-ink devices such as BOOX, built around one guarantee: never show content the user hasn't read. Its distinctive AI features are grounded in reading progress: 'Previously on…' recaps generated only from finished chapters; tap-any-name 'Who is this?' character lookups that refresh who a character is, what they've done, and why they matter up to the current reading position (extending across earlier finished books in a series for Pro); and 'Explain', which rewrites dense or archaic passages into plain English, helpful for second-language reading. Other features: save quotes as shareable images, reading stats (streaks, session time, yearly heatmap), community trends, and a library with search, filters, status chips (Reading/To Read/Finished), series grouping, and EPUB import including Calibre Wi-Fi sync. Free
RESEARCHED BUILD PROMPT
Give this to your coding agent.
Build a focused reading companion in the spirit of Recall Reader: an Android EPUB reader whose core promise is spoiler-free context, with every AI feature grounded strictly in the reader's progress, never in unread text. Core workflow: (1) open a book and get a 'Previously on…' recap generated only from chapters the user has finished; (2) tap any character name for a 'Who is this?' profile limited to events, motives, and relationships up to the current position; (3) long-press a passage for a plain-English 'Explain' (dense prose, archaic language, or second language); (4) save quotes as shareable images; (5) track streaks, session time, and progress. User-facing requirements: a distraction-free EPUB reader, chapter and in-book progress tracking, library with status chips and series grouping, character mention detection with names linked to the reading position. Technical requirements: EPUB parsing (Readium/ebookjs), local SQLite/FTS for library and metadata, LLM calls where prompts inject only read-slice text plus a strict no-spoilers system constraint, offline-first storage, and an e-ink-friendly UI (high contrast, no animations, large touch targets). Do not copy Recall Reader's brand, proprietary assets, or UI—build an original minimal interface. Explicitly out of scope: cloud sync/backup, community trends, Calibre sync (local file imports only). Deliver a README covering setup, architecture, and important limitations: AI latency/cost, token limits on long books, and the honest caveat that the spoiler guarantee is best-effort, not provable.