ReadingCAN I VIBECODE
Reeder?
BUILD FIRST
- One defined user and a repeatable end-to-end job
- A small, clear data model with sign-in only if it is genuinely needed
- Loading, empty, error, and success states that make the workflow feel complete
LEAVE FOR LATER
- Large integration marketplaces
- Multi-region scale and enterprise administration
- Every power-user setting from the established product
RESEARCH NOTES
What this tool actually does.
Reeder is an Apple-only reading app (iOS 17+/iPadOS 17+/macOS 14+) unifying RSS feeds, podcasts, videos, and social-media posts into one timeline. It replaces unread counts with synced scroll positions: reading position syncs per feed, folder, filter, and the Home timeline, pushed via iCloud within seconds. Users create custom folders and filters (by keyword, media type, or feed type) and save links via the share sheet into built-in tags (Later, Bookmarks, Favorites) or custom tags, with keyboard shortcuts L, B, F. A subscriber feature turns any tag into a public, auto-updating JSON feed (last 50 items) hosted on reederapp.net, viewable in a browser or any JSON-feed-capable reader. iCloud sync covers subscriptions, timeline position, and tagged items only; content is fetched directly from sources. A separate legacy product, Reeder Classic, is a traditional RSS reader with iCloud read-lat
RESEARCHED BUILD PROMPT
Give this to your coding agent.
Build a web-based "reader inbox" prototype inspired by Reeder's workflow. Core loop: the user adds RSS/Atom feed URLs and YouTube channel URLs; the app fetches and merges new items into a unified reverse-chronological timeline where each item shows title, source, type (article/video/audio/social), and a snippet. Clicking opens the original page in a new tab. The user's reading position (last-scrolled item) persists per timeline and per source folder; restores on return. Users can create folders and filter timelines by keywords or media type. A 'Later' list lets users save links via a bookmarklet, and each tag/folder can be published as a static JSON Feed endpoint. Technical requirements: Node.js backend with a fetch-parse pipeline (e.g., fast-xml-parser for RSS, YouTube RSS feeds for channels), SQLite for subscriptions/items/positions/tags, a simple REST API (Express) and vanilla/React frontend; use JSON Feed format for exported tags. Implementation approach: polling fetch every 10 minutes with upserts, scroll tracking via IntersectionObserver, and per-tag pre-rendered JSON files. Do not copy Reeder's brand, iconography, or pixel-specific UI; produce an original minimal design. Out of scope: native iOS/macOS apps, iCloud sync, push notifications, authentication, full-text parsing, and podcast playback. Deliver a README covering setup (install, env, seed database), architecture, and known limitations (JSON feed capped at 50 items, fetch rate limits, no auto-pagination for large timelines).