Wedlock
Wedding planner app with tools for managing guests, guest lists, and tasks.
- Logo Design
- Laravel
- Filament
- Inertia.js
- Tailwind CSS
The Problem
Wedding Planning is Overwhelming
Couples juggle checklists, RSVPs, budgets, dietary needs, guest groupings, and countless small tasks—often scattered across spreadsheets, WhatsApp groups, and sticky notes. There was no simple, free tool that brought all of these essentials under one roof with a clean, usable interface.
The Solution
What Wedlock Does
Wedlock is a web-based wedding planner that helps engaged couples organise their big day from start to finish. The aim was to create a tool that feels supportive rather than overwhelming—giving couples clarity during an otherwise stressful time.
To-Do Tasks
Customisable deadlines with progress tracking to keep everything on schedule.
Guest Lists
Group organisation, RSVP and attendance status tracking all in one place.
Budget Tracking
Visual spending breakdowns to help couples stay on top of costs.
Countdown & Reminders
Days-to-go counter with milestone notifications to reduce last-minute stress.
My Role
Sole Creator, End To End
I was the sole creator of Wedlock, handling everything from initial concept through to production deployment.
What this included
- Product vision & user journeys
- UI and UX design
- Frontend development
- Backend architecture
- Authentication & security
- Deployment & maintenance
Tech Stack
Built for Performance and Maintainability
The stack was chosen to balance developer efficiency, performance, and long-term maintainability. SPA-like experience without a separate API layer.
Technologies Used
- Laravel
- Vue.js
- Inertia.js
- Filament
- Tailwind CSS
- MySQL & PostgreSQL
User Feedback & Learnings
What I Learned From Real Usage
Early users consistently highlighted how Wedlock's simplicity helped them stay organised without feeling overwhelmed. Couples reported fewer missed tasks, better budget visibility, and less reliance on scattered tools.
Usability matters more than feature count
Users appreciated what the app didn't do as much as what it did. Restraint in features led to better adoption.
Small UX decisions have big emotional impact
Inline editing, smart defaults, and immediate feedback made the difference between "nice" and "I love this".
Iterating on real behaviour beats assumptions
Features I thought were essential went unused. Simple features I nearly cut became favourites.