One shared gallery. Every photo. Full resolution.
I was at my cousin's wedding three years ago when I noticed something odd. The couple had hired a photographer. The guests had taken 400 photos on their phones. And none of those guest photos existed in any shared place. They were scattered across 60 different camera rolls, most of them never backed up, most of them forgotten within a week.
The moment we realised the problem wasn't really about photos
We spent the first few months of Poolr building a product that nobody actually wanted. It was clever. It had filters and tags and albums within albums. The issue was simple: we were solving for organisation when the real problem was collection.
Event hosts didn't need a better photo library. They needed their guests' photos in one place, full stop. And they needed it to work instantly. No app installs. No account sign-ups. No friction. Just scan a QR code with the phone that's already in your pocket, pick photos from your camera roll, and go.
We stripped everything back. Removed the login screen. Removed the app store requirement. Removed the assumption that people would spend ten minutes reading an onboarding tutorial at a wedding reception. What remained was the core ask: collect every photo, in full resolution, in one shared gallery.
Why full resolution mattered more than we expected
When we first launched, we compressed images. It saved bandwidth, reduced server costs, made uploads faster. A customer sent us a message about two weeks in. She'd hosted a 40-person birthday party, collected 300 photos, and wanted to print a photobook from the gallery. The images were soft. The text on birthday banners wasn't readable.
We changed our mind that day. We committed to storing and serving every photo at the resolution the guest's phone captured it at. It meant higher server costs. It meant slower uploads for some users on weak connections. But it meant that months or years later, when someone wanted to print a photo from the gallery, or display it on a wall, or crop it for a frame, the quality was there.
This became the baseline for everything else we built. The live photo wall display that shows images on a screen during the event. The automated photobook generation that turns the gallery into a printed keepsake. The ability for a host to bulk download everything in ZIP format and archive it properly. All of it hinges on the fact that the original files aren't compromised.
The host's gallery, not the platform's gallery
There's a difference between collecting photos and owning them. We built Poolr so the host is always the owner. The photos live in their gallery. Their guests can see them, but the host controls who can access what, when to take the gallery down, and what happens next.
For most events, that's the Free tier or the Moment tier. A modest gathering, a clear endpoint. For bigger occasions, couples choose Occasion, which means the gallery never expires and the resolution never degrades. Some hosts want more; they choose Forever and get two years of retention plus the ability to generate an automated highlight reel using face recognition.
The point is that Poolr sits between the host and their guests. We're not trying to be your long-term phone storage. We're not a social network where your photos live forever in some corporate database. We're the place where event photos, from every person who attended, get collected properly and then do something useful. Get printed. Get displayed. Get archived.
What we learned from shooting weddings, birthdays, and corporate events
Our early users taught us what full-resolution collection actually unlocked. Wedding photographers started using Poolr alongside their own work, offering clients the unfiltered guest experience in addition to the professional shots. They liked that they didn't have to spend three hours downloading photos from 40 different guest emails.
Church administrators discovered that Occasion gallery footage became the primary record of a congregation event. Sports clubs found that parents wanted full-resolution shots of their kids, not compressed thumbnails. Corporate teams realised that having every attendee's perspective on a conference or offsite created a richer memory than any one photographer could capture.
Each of these use cases needed the same thing: reliability. Full resolution. No quality loss. No surprises when you came back to the gallery months later expecting a usable photo.
The quiet work of staying out of the way
Building full-resolution collection at scale isn't glamorous. It's choosing the right storage infrastructure. It's handling network failures gracefully so that guests on patchy WiFi at an outdoor festival can still upload without losing their photo halfway through. It's making sure the live moderation queue works fast enough that a host can approve photos in real time if they're displaying on a live wall.
None of this is visible to the user. The guest scans the QR code, picks their photos, taps upload, and it works. The host checks their gallery later and sees everything in perfect quality. That's the goal. The technology should be invisible.
What makes this possible isn't one big clever idea. It's a hundred small decisions made in the right direction. Choosing to store originals instead of compressed versions. Choosing to make the upload flow four taps instead of eight. Choosing to let someone see their contribution in the gallery instantly, even if moderation approval is pending. Choosing to serve the full-resolution file to anyone viewing the gallery, not a smaller version.
Three years on, I still think about that wedding and all those forgotten photos scattered across 60 camera rolls. If you're organising an event soon, ask yourself this: when it's over, what would you actually want from your guests' photos? And then ask whether the tool you're considering actually gives you that, or whether it's solving problems you never had in the first place.