Can Raindrop.io be vibe coded?
Visual bookmark manager for saving, tagging, and searching links
A personal bookmark saver with tags, full-text search, and screenshots is a very tractable small app.
Jump to the build brief ↓Checked Jul 2026
What you pay today, before any DIY hosting
high editorial confidence
Buildability by layer
Screens, forms, and focused interactions
The repeatable job the product performs
Availability and legality of required data
Uptime, queues, support, and maintenance
Security, compliance, and user confidence
The achievable core
- Build a browser extension/bookmarklet, save URL metadata to SQLite/Postgres, tag it, optionally archive page text, and provide search.
- Build a focused single-user workflow with real persistence, search, and export.
- A responsive interface with real empty, loading, success, and error states.
The parts a prompt cannot buy
- mobile apps
- browser-extension polish
- permanent archiving
- visual previews
- The last 20 percent is sync, migration fidelity, speed, and edge cases.
Why people still pay
They pay because bookmarks are boring until import/export, search, mobile, and extension reliability matter.
The last 20 percent is sync, migration fidelity, speed, and edge cases.
The brief
Context, requirements, acceptance criteria, non-goals, and the full production standard — as Markdown, ready for any coding agent.
Build brief — a focused alternative to Raindrop.io
Context
**Raindrop.io** — Visual bookmark manager for saving, tagging, and searching links. It currently costs $3/mo.
A personal bookmark saver with tags, full-text search, and screenshots is a very tractable small app.
This brief describes a focused, single-operator replacement for the part of Raindrop.io 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 extension/bookmarklet, save URL metadata to SQLite/Postgres, tag it, optionally archive page text, and provide search.
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
Browser extension or bookmarklet.
Small hosted backend or local database.
Page metadata/extraction library.
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 bookmark manager to replace Raindrop.io. Requirements:
A local web app: Node + Express + better-sqlite3 on localhost:4040, server-rendered,
minimal JS.
Save via a bookmarklet that POSTs the current URL to /save; the server fetches the
page, pulls title/description/og:image with metascraper, and stores the readable
article text (@mozilla/readability) for search.
Bookmarks take free-form tags (comma entry, autocomplete from existing tags) and an
optional note.
Full-text search across title, note, and archived page text with SQLite FTS5; filter
by tag, newest first.
List view: favicon, title, domain, tags, saved date. A weekly node-cron job re-checks
links and flags 404s.
Import from a Netscape bookmarks HTML export; export everything as JSON and CSV from
an /export route.
Binds to localhost only; no accounts, no telemetry, the whole archive is one SQLite
file I can back up.
Out of scope: mobile apps and full page-snapshot archiving, the stored text is the
archive. No team collections.
README: how to install the bookmarklet and where the DB file lives.
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:
Mobile apps.
Browser-extension polish.
Permanent archiving.
Visual previews.
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.
Risk
**Manageable.** A personal version is realistic if you test the critical journey and keep reliable backups.
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:
[linkwarden](https://github.com/linkwarden/linkwarden) — Open-source bookmark manager with archiving, collections, and collaborative saving
Generated by [Can It Be Vibe Coded?](https://www.canitbevibecoded.com) · Full report: https://www.canitbevibecoded.com/raindrop-io
You still own the product
- 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.
Open-source prior art
Before you start
Can Raindrop.io be vibe coded?
Yes, for personal use. A personal bookmark saver with tags, full-text search, and screenshots is a very tractable small app.
What can an AI coding agent reproduce from Raindrop.io?
Build a browser extension/bookmarklet, save URL metadata to SQLite/Postgres, tag it, optionally archive page text, and provide search. Build a focused single-user workflow with real persistence, search, and export. A responsive interface with real empty, loading, success, and error states.
What will a DIY Raindrop.io replacement still be missing?
mobile apps; browser-extension polish; permanent archiving; visual previews; The last 20 percent is sync, migration fidelity, speed, and edge cases.
What do I still own after building a Raindrop.io alternative?
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.