SoloEra solo activities, solo maxxing, sidequests, challengeEvery guest's wedding video, cut into one film
Already built this?
Show what you made. Add your app to this idea.
Guests upload whatever they filmed — thirty seconds of the ceremony from row
four, a table shot, someone's phone catching the first dance from the side. It
gets assembled into one film from every angle.
The material already exists at every wedding. Two hundred clips scattered
across forty phones, watched once and never again. Meanwhile the couple pays
€3,000 for a videographer covering one position at a time.
The audio is what makes it possible. Forty phones recording the same speech
give you forty timestamps of the same waveform, so clips can be aligned to the
second without anyone tagging anything. That alignment is the whole product;
without it you have a folder, not a film.
The hard part is upload. Guests will not install an app at a wedding, and they
will not remember afterwards. It has to be a link in the group chat that opens
a browser and takes one tap. Anything more and you get four uploads instead of
sixty.
Second hard part: most of the footage is bad. Shaky, dark, someone's thumb.
Cutting well means being ruthless, and the couple will still want the clip
where grandmother is visible even though it's out of focus. So it needs an edit
you can override, not a finished file you accept.
And the sensitive part: guests filmed each other. Someone will want their clip
removed. There has to be a way to do that without an account, or it becomes a
problem at exactly the wrong moment.
- Pricing thoughts
- Free for guests to upload — any friction there and there's no material. The couple pays, €99 to €199 for the finished film. That's a tenth of a videographer and it's a purchase made once, at a moment when nobody is price-sensitive.
- Talk to @peekly_app
- @peekly_appReach out if you want to build it, build it together, or just ask what they had in mind.
- Prompt copied
- 1 times
Generated build prompt
Build every guest's wedding video, cut into one film. Context: Guests upload whatever they filmed — thirty seconds of the ceremony from row four, a table shot, someone's phone catching the first dance from the side. It gets assembled into one film from every angle. The material already exists at every wedding. Two hundred clips scattered across forty phones, watched once and never again. Meanwhile the couple pays €3,000 for a videographer covering one position at a time. The audio is what makes it possible. Forty phones recording the same speech give you forty timestamps of the same waveform, so clips can be aligned to the second without anyone tagging anything. That alignment is the whole product; without it you have a folder, not a film. The hard part is upload. Guests will not install an app at a wedding, and they will not remember afterwards. It has to be a link in the group chat that opens a browser and takes one tap. Anything more and you get four uploads instead of sixty. Second hard part: most of the footage is bad. Shaky, dark, someone's thumb. Cutting well means being ruthless, and the couple will still want the clip where grandmother is visible even though it's out of focus. So it needs an edit you can override, not a finished file you accept. And the sensitive part: guests filmed each other. Someone will want their clip removed. There has to be a way to do that without an account, or it becomes a problem at exactly the wrong moment. Requirements: - Ship the smallest version that delivers the core value above, nothing more. - Pick a stack you can deploy in a day, and state the choice before writing code. - Handle the empty state, the error state and the offline case explicitly. - Pricing to build toward: Free for guests to upload — any friction there and there's no material. The couple pays, €99 to €199 for the finished film. That's a tenth of a videographer and it's a purchase made once, at a moment when nobody is price-sensitive. Start by listing the screens, then build them one at a time.