Can I vibecode Wanderfugl?

KINDA · weekend project

price $9/moyou'd save $108/yrbuild time one sittingcategory ✈️ travelreplaced by 0 people

Trip planning is one of the most one-shottable categories there is: it is days, places, times, notes and a map, which is a CRUD app with a calendar view. An agent can give you a local itinerary builder with day-by-day cards, confirmation numbers, an ICS export and a pinned map in a single sitting, and it will feel better than a spreadsheet. The gap is everything that touches live travel data: flight and hotel prices, schedule changes, timezone-correct arrival math, place search with real coordinates, and inbox parsing of booking emails. If the paid product's value is mostly structure and a nice UI, self-hosting wins; if it is live data feeds or a polished phone app you use offline in an airport, it does not. Rate it kinda until you know which of those you are actually paying for.

the prompt

Build a local-first trip planner web app called Fugl. No accounts, no cloud, no telemetry.

Stack, non negotiable:
- Next.js with the App Router and TypeScript
- SQLite via better-sqlite3, file at ./data/fugl.db, created and migrated on first run
- Tailwind for styling, no component library
- Leaflet with OpenStreetMap tiles for the map
- Runs with: npm install, npm run dev

Data model:
- Trip: id, name, destination label, start date, end date, notes, home timezone
- Item: id, trip id, kind (flight, train, lodging, activity, food, note), title, start datetime, end datetime nullable, timezone, location name, lat nullable, lng nullable, confirmation code, url, cost, currency, notes
- Packing item: id, trip id, label, packed boolean

Features in scope:
- Trip list page, create and edit trips
- Trip detail page grouped by day, each day showing items sorted by start time, with kind icons and a running per-day cost total
- Add and edit items in a side drawer, with lat and lng entered manually or pasted from a maps URL
- Map panel showing all items with coordinates for the trip, pins numbered by day
- Packing list with checkboxes, persisted
- Export trip to .ics with one VEVENT per item, timezone aware
- Printable itinerary view at /trips/[id]/print, clean single column, no nav chrome
- JSON export and import of a whole trip
- Full text search across item titles, notes and confirmation codes

Explicitly out of scope:
- Flight, hotel or price lookups of any kind
- Email parsing, OAuth, sharing links, multi user
- Push notifications and native apps

Use .env for the optional map tile URL and nothing else. Seed one demo trip with three days of items so the UI is not empty. Write a README with run steps and a one line note that all data stays in ./data.

$ open in your agent (prompt prefilled, you press enter) or copy it raw · this prompt is generated from the build plan · improve it via PR

why people still pay

Because the hard part of trip planning is not storing the plan, it is getting the plan in and out without typing. Forwarding a confirmation email and having flights, seats and hotel nights appear correctly, with the right timezones and the right dates, is worth money to people who travel often. Add a phone app that works in an airport with no data and a share link your travel partner can actually read, and a self-hosted version starts to feel like homework right when you least want homework.

what you lose

xLive flight, train and hotel pricing or availability

xAutomatic booking email parsing into your itinerary

xA real mobile app with offline access while travelling

xTimezone and schedule-change handling done correctly by someone else

xSharing a polished read-only itinerary with travel companions

prior art · use these instead of building, if you'd rather

Nothing worth pointing at. That's why the prompt exists.

share on X ↗"I just replaced Wanderfugl ($9/mo) with one prompt"