Maciej Topór

Marry Planner: your wedding, organized - Plan your wedding together, not in a spreadsheet

by
Marry Planner is a wedding planning app built for couples, not just brides. Plan together in real time with your partner or wedding coordinator across Web, iOS, and Android. What's inside: • Budget tracker that actually reflects what you've paid vs. owe • Smart checklist with timelines tied to your wedding date • Guest list with RSVPs, meal prefs, and plus-ones • Drag-and-drop seating chart • Shared access, no more "did you book the florist?" texts

Add a comment

Replies

Best
Maciej Topór
Maker
📌
Hey Product Hunt 👋 Six months ago my fiancée and I were trying to plan our wedding out of a Google Sheet. Budget on one tab, guest list on another, seating sketched in a Google Doc, vendor contacts scattered across both our phones. Every conversation started with "wait, which version is current?" We tried the existing wedding apps and bounced off all of them — they were either built for one user (the bride), buried the features under bridal-magazine content, or didn't sync between us in real time. The collaboration piece was non-negotiable for us, and somehow it was the hardest thing to find. So I started building Marry Planner as a tool just for us. Two months ago I launched it publicly on Web, iOS, and Android, and we're now at ~200 downloads with early feedback that keeps me building. What's different: • Built for two from day one — both partners (and optionally a coordinator) share the same live data • Calm UI — no listicles, no ads, no "23 dress trends you need to know" • Cross-platform — start on the couch on web, finish on the bus on mobile A few things I'd genuinely love feedback on: For anyone who's planned a wedding — what's the one task you wish an app had handled that none of them did? For makers in seasonal / one-time-use verticals — how do you think about retention when users churn after the event? For couples currently planning — would you trust an app with vendor contracts and payments, or is that a step too far? Happy to answer anything about the build, the launch, or the ~3 rewrites the seating chart UI took to get right.