🎁 Podaruj.me
A wishlist sharing platform — create wishlists, share them with anyone, and let people reserve gifts without spoiling the surprise.
Podaruj.me solves a universal problem: buying gifts without duplicates and awkward guessing. A user creates a wishlist for any occasion — birthday, holidays, wedding — shares a link, and guests can browse and reserve items instantly. No account required for guests. Three privacy modes let the list owner control exactly how much they see, from full transparency to complete surprise.
🎬 See it in action
🔊 Unmute for English voiceover · 🇵🇱 Wersja polska
https://github.com/user-attachments/assets/08b42f80-7438-4cbd-ac0a-e5829cdee67f
Three things that make this more than a CRUD app:
🔒 Privacy modes enforced at the database level — three reservation visibility tiers, including a Full Surprise mode where even the list owner can't see who reserved what
🎯 Guest-first access — no account needed to browse or reserve. One tap from a messenger link and you're in
🤖 Built through agentic orchestration — zero hand-written code, fully documented process from prompt to production (see docs/)
Why I Built This
Gift lists sound simple — until you think about privacy. Who sees what? Can the birthday person find out what's coming? What happens when the event passes? These questions turned a "simple CRUD app" into a product with real UX depth: three privacy modes, a Full Surprise lifecycle with draft/publish/reveal stages, guest access without sign-up walls, and a celebration screen after the event.
I wanted a portfolio project that demonstrates product thinking, not just code output — something with real user flows, edge cases worth solving, and a UI polished enough to pass as a shipped product.
Built in 3 days — from concept to deployed product, using document-driven agentic orchestration.
Features
🔒 Privacy That Actually Works
The core differentiator. Each list has one of three reservation privacy modes, enforced server-side — not just hidden in the UI:
- Buyer's Choice — the person reserving decides whether to reveal their identity or stay anonymous
- Visible — everyone sees who reserved what (great for coordinated gifts)
- Full Surprise — the list owner sees nothing. Items appear unreserved. Maximum surprise, with a reveal moment after the event
Full Surprise lists have a dedicated lifecycle: they start as drafts (invisible to guests), and once published, items are locked to prevent the owner from reverse-engineering reservations through edits.
🎯 Zero Friction for Guests
Guests arrive via a shared link or QR code and can browse and reserve immediately — no sign-up, no login wall. Just enter a nickname and go. This was a deliberate UX decision: most users arrive through a messenger link on their phone, and any friction means drop-off.
📋 Lists & Items
- Create multiple lists with occasion types, event dates, and optional countdown timers
- Items support links, prices, images, and three priority levels — but only the name is required
- Drag & drop reordering via
@dnd-kit, plus 8 sort options
- Slug-based shareable URLs with automatic redirect history on rename
📤 Sharing
- Direct link sharing with a clean, readable slug URL
- Email sharing via
mailto: with a pre-composed friendly message
- QR code generation with download and print options
- Real-time animated countdown to the event
📊 Dashboard
- My Lists — overview with item counts, countdowns, draft/closed badges
- My Reservations — everything you've reserved on other people's lists, with cancel option
🔄 List Lifecycle
Lists aren't just static pages — they have a full lifecycle:
- Draft (Full Surprise only) → owner prepares items privately
- Published → open for browsing and reservations
- Closed → after event date/time or manual close. No new reservations.
- Celebration → stats summary, reservation reveal, confetti animation 🎉
🌍 Bilingual
Full English and Polish support with a language switcher. Built with next-intl.
👤 Profile & Auth
Passwordless authentication via Google OAuth or magic link. Profile settings with display name, avatar (synced from Google), and full account deletion with cascade cleanup.
How It Works
Owner Guests
│ │
├─ Creates list │
├─ Adds items │
├─ Chooses privacy mode │
├─ Shares link / QR / email ──→│
│ ├─ Opens link (no account needed)
│ ├─ Browses items
│ ├─ Reserves with nickname
│ │
├─ Sees reservations │
│ (per privacy mode) │
├─ Event passes → list closes │
└─ Celebration + reveal 🎉 ┘
Development Approach
I deliberately chose to build this through document-driven agentic orchestration rather than writing code by hand. The goal was to explore and demonstrate a workflow that's becoming increasingly relevant: treating AI agents as an implementation team that you direct through structured documentation, iterative review, and precise prompts.
This isn't about avoiding code — it's about operating at a higher level of abstraction. Defining the product, validating the output, maintaining quality, and steering agents when they drift. The same skills that make a good tech lead or product engineer, applied to a new kind of toolchain.
Built in 3 days. Zero hand-written code. Full product control.
This is the beginning of the README. Read the rest at the original. Read the full README ↗
