← posts

We'll miss half of our own wedding, so I built an app for our guests' photos

· 4 min read

We're getting married on 24 October, and we already know we'll miss half of it. The bride and groom spend the day making sure things run smoothly and everyone's having a good time. Meanwhile our guests will be catching the small moments we never see, and those are the photos I want most.

Getting them is the problem. I've been the guest in this situation. You're stuck on an upload page that only works if you stay on it, and the moment you leave the web view the upload is gone. Or you're stuck in an AirDrop or Bluetooth session, waiting for a transfer to finish. Or you send them over a messaging app, and what arrives is a squashed copy with the original capture time gone. So most guests don't bother.

At the events I've been to, only a handful of people actually share their photos and videos. The rest don't, either because they don't understand how, or because they plan to do it later, forget, and never do. Normally you'll see a few people upload on the day, then another handful in the week or so after. Most of the memories stay on people's phones, with no way for you to see them.

I went looking for something that fixed this. After close to a month of researching competitors, every option fell into one of two groups: expensive for what it does, or a basic web page with the same stay-until-it's-done upload I'd hated as a guest. So I built GuestLens.

What it's trying to do

The rule behind every decision is that the guest should have to do as little as possible. Guests have already spent time and money on your event. Sharing photos afterwards shouldn't feel like homework. I set myself one test: my grandmother had to be able to use it, however limited her technical ability. That ruled out sign-up, long flows and anything that needs explaining.

The result keeps the original file at full quality and the original capture timestamp, and it asks guests for almost nothing. It also seems to help beyond the individual guest: when one person shares without effort, others are more likely to follow.

The name comes from what you get at the end: your event seen through your guests' lenses, including the moments you were too busy to catch yourself.

Our wedding

We've set up our own wedding the way any host would, with accent colours to match the wedding's theme and a header image.

Our event has 1 GB of storage per guest. That's partly so no guest ever hits a limit at our wedding, and partly so I get real numbers from an actual wedding. How much a guest really uploads is the thing I most want to learn.

What we're hoping to find in the gallery afterwards is everything we couldn't see: the moments that happened while we were off taking photos or talking to someone else, the small things you don't think to capture, maybe a video of the guests just having fun.

If something goes wrong on the day and I end up pulling out my MacBook to get it fixed so people can actually upload photos, there'll be a follow-up post about it. If there's no drama, there won't be one.

As a guest

All you need to know is your own name (or nickname). The host can give you a QR code, a link, a text or the actual code. Your name is attached to your uploads so the host and other guests know who shared what, and there's no account to create.

If you tap a link and don't have the app, it opens the App Clip. If you do, it opens the full app. Either way, there's no App Store detour first.

You don't have to do anything during the event itself. The host sets a window for how long uploads stay open, so you can add everything later. You can also capture photos and video inside the app, and those upload straight away. Either way, uploads keep their original quality and timestamp, and there's no artificial limit on video size or length. The ceiling is your phone.

It's one shared gallery, so you can also browse and download what everyone else took, and react to photos with emojis. I added reactions so the gallery feels like something worth opening, not a static wall of photos.

The benefit to the guest is that sharing takes a minute, you don't have to stay on a page, and you get everyone else's photos back in return.

As a host

A host creates an event with a name and a date. You can match it to your event with accent colours and a header image, such as a photo of the couple at a wedding. Every event needs an upload window, which sets how long guests can add photos and videos. Guests join with the event code, a QR code or a link.

Every host gets 500 MB free to try it before paying anything. After that it's per event, not a subscription, and GuestLens estimates the storage you need from how many guests you expect. If you go over your limit, uploads carry on for a good while instead of stopping, so a guest isn't blocked from sharing a memory. However, we'll keep you up to date by sending you notifications when you're getting close to your storage limit or have gone past it. We'll also notify you ahead of your event expiring, but when it does expire, everything in it is permanently wiped from the servers, so save what you want to keep before then. The app page has the full details.

The benefit to the host is that you stop chasing people for photos afterwards and you get the originals when you do. It isn't only for weddings either. It works for anything from a night out with friends, where it replaces sharing photos over Messenger, to a corporate event.

How it got built

I'm an iOS developer who had never done proper web development, and I didn't want to run and host an app on top of planning a wedding. That's why I spent a month looking for something to use instead. When nothing worked, I built it myself. How I planned the architecture and used AI to get the app ready in about two months is in How I built GuestLens around planning a wedding.

GuestLens is out now on iOS and Android.