Heirlooms

The platforms wedding photographers use are mature and, on the photographer’s side, genuinely good. But almost all of them treat a gallery as a transaction that closes. There is an expiry date, an archive fee, and eventually an email that reads like a countdown. The link is storage the photographer rents on the client’s behalf.

Meanwhile the couple’s actual job was never “review 4,507 photographs”. It is to find the twenty they’ll use, send four to family without making anyone sign up, and still have all of them in ten years. Almost nothing in the category is designed for that.

So I took the opposite position and designed the whole product from it: a delivered gallery never expires, and everything else follows from having to make that work: for the couple, and for the business that pays for it.

The client side had to work with no account and no instructions, a link in a text message. That constraint removed a lot of options: no onboarding to explain anything, no settings to hide complexity in, and every important action reachable from the first screen.

The studio side is the opposite: a workspace someone signs into weekly, where depth is welcome and density is a feature. Same content underneath, two completely different structures over it.

Three questions had to be settled before anything was drawn properly: where scene navigation lives, whether favourites are a filter or a place, and how much chrome can sit on a photograph before it stops being a photograph.

The second one mattered most. As a filter, favourites are something you have to remember; as a place with its own address, they become somewhere you return to, which is what let them turn into a deliverable later.

Monica and Chris’s gallery is 4,507 photographs across four days and two ceremonies: a mehendi, an Indian ceremony and reception, and an Irish-American wedding day. A flat grid of that has no shape; every scroll looks like the last one. So the gallery arrives already divided into scenes, with counts, and the rows are justified rather than square-cropped so portrait and landscape frames keep their proportions. That last part sounds cosmetic and isn’t: square crops cut the composition out of every photograph in the set.

The interface itself is deliberately quiet: a warm paper ground, one ink, and a single brass accent that only ever means you did something here. Nothing in the chrome competes with the work it’s framing.

Culling and editing is the photographer’s craft. Building the gallery is admin, and it happens at eleven at night, so the studio side is designed around removing the second pass entirely. Photographs are grouped into scenes as they upload, proposed from capture time and setting, and the photographer renames or merges rather than sorting from scratch.

The dashboard answers the question that actually gets asked between weddings: not “what have I uploaded” but “who hasn’t opened theirs”. Delivery status, client activity and waiting album selections are the primary content.

Permanence has to survive the business model too, so I framed it as a retention feature rather than a cost centre: a couple who can still reach their photographs in ten years is a couple who knows exactly who photographed them. That’s an argument, not a proof, and I’ve flagged it as one below.

Every colour in this product sits behind photographs, and wedding photographs are already warm, saturated and busy. So the palette is deliberately narrow: a paper ground, one ink, and a single brass accent. No second accent colour was allowed in, which meant status had to be carried by shape and placement rather than by inventing new hues.

Components were built as variants from the start, because the states are where a photo product breaks: a favourite that’s already been sent, an upload halfway through, a gallery with no cover chosen yet. Drawing only the happy path would have hidden all three.