shipped
live, App Store + Play Store
Wedding planner app, vendor marketplace + real-time bride/vendor messaging.
02 · Outcomes
Numbers, not adjectives. The stats below are pulled from production. Anything still live, still measured.
shipped
live, App Store + Play Store
iOS + Android
shared business logic
bride ↔ vendor chat
shared timeline, same threads
frontend scope
from spec to store review
03 · Overview
Wedding planning is a logistics problem disguised as a romantic one. Ring Leader treats it that way. Venue, catering, music, decor, guest list, seating, all in one app. Real-time chat with vendors on a shared timeline so the bride and the florist aren't in two different conversations on two different apps.
04 · Gallery
Secondary mockups, detail crops, mobile and desktop variants. Click any shot to open it full-size.
05 · Process
Four phases. Each one with a deliverable the client could see, not a slide deck of intent.
Wedding planning is a logistics problem disguised as a romantic one. Mapped the actual coordination — venue, catering, music, decor, guest list, seating — the small-talk pieces hide a project-management spine. Brief was: bride and vendor on one timeline, not two.
React Native frontend for cross-platform shipping. Redux Toolkit for shared state across cart, plans, and chat. Socket.IO sidecar for the bride ↔ vendor messaging rail. Frontend role focused on the app surface + real-time integration.
App-first iteration. Match flow, vendor browse, booking timeline built in mobile-native rhythms. The chat sync between bride mobile and vendor web portal was the trickiest piece — message ordering, read receipts, and notification cadence all needed to stay coherent across two surfaces.
Live since 2023. Cleared App Store + Play Store review on first submission. Vendors run listings + bookings via the partner portal; brides handle the full plan from the mobile side.
06 · Decisions
Tech is downstream of decisions. These are the calls made early enough to compound the right way. The ones a code review six months later still agrees with.
Cross-platform with shared business logic. Same brain, two surfaces. iOS + Android shipping from a single codebase, faster iteration, no dual-team coordination tax on every feature.
Bride and vendor on the same thread, same timeline. Polling would have left messages stale up to the refresh interval; sockets keep both sides honest at sub-second latency, which is the whole point.
Cart, plans, threads, timelines — all shared between bride app and vendor portal. Same store shape on both surfaces, so a state change in one renders cleanly in the other without divergent reducers.
06 · Let’s build
I take 4–5 freelance projects a year. Cold pitches welcome. I reply within 24 hours on weekdays.