Vibe-coded side projects by Andreas Sander.
Ideas that turned into working software with an AI pair programmer in the loop. Local-first by habit, shipped when they're useful, polished when they're fun.
Everything in this org started as a "what if…" and was built largely by talking to a coding agent. That means:
- Fast from idea to something runnable. Most projects went from empty repo to daily use in days, not months.
- Real engineering underneath. Tests, CI, ADRs, and docs where they earn their keep. Vibe-coded, not throwaway.
- Local-first, no accounts. Data stays on your device unless you explicitly opt into sync.
- Scratching my own itches. If a project is useful to you too, great. If not, that's fine as well.
| Project | What it is | Stack | Try it |
|---|---|---|---|
| Ferrico | Fast, local-first bookmark manager for macOS, Linux, and Windows. Folders, tags, fuzzy search, duplicate and dead-link detection, optional Google Drive sync, browser extension, read-only Android companion. | Tauri 2 · Rust · React 19 · SQLite | Website |
| Kann ich lüften? | Should I open the windows right now? Compares absolute humidity inside and outside, checks for condensation on cold surfaces, and suggests how long to air the room. Installable PWA, works offline. German UI. | TypeScript · Vite · Vitest · Open-Meteo | Open app |
| Racing game | 2D racing game with neuroevolution AI opponents. Started in Love2D/Lua, ported to Rust on Bevy. The pure simulation lives in its own engine-free, unit-tested crate. | Rust · Bevy 0.16 · Lua (legacy) | cargo run |
| Primico | Native Android and desktop todo app. Importance first, due date breaks ties, with recurrence that understands both calendar rules and "n days after completion". Quick add in English and German, tags, subtasks, attachments, widgets. Fully usable offline and signed out; sync is an optional sign-in against a Neon project you host yourself. (Formerly Cadence.) | Kotlin · Compose Multiplatform · SQLDelight | Website · Android APK |
| Inoswipe 🔒 | Swipe through your Inoreader backlog two articles at a time: keep one, mark the other read. Inbox zero, but fun. Tokens never reach the browser thanks to a small Hono backend. | React 19 · Zustand · Hono · Node 24 | private |
🔒 = private for now. Might open up once they've settled.
The workflow is roughly the same across repos:
- Describe the thing. Argue with the agent about the design until it's sane.
- Let it write the boring parts, review the interesting ones.
- Tests and CI from the first commit, so the next vibe session doesn't break the last one.
- Write down decisions (ADRs) so future-me and future-agent know why.
Most repos carry a CLAUDE.md or similar agent guide that explains the architecture and commands. That file is usually the best place to start reading.
Issues and pull requests are welcome, but expectations should match the label on the box: these are hobby projects, maintained in evenings and weekends. Bug reports with reproduction steps get looked at. Feature ideas are read with interest and implemented on vibes.
- Blog and everything non-vibe: andi1984.dev
- Main GitHub account: @andi1984
