An event ends and everything it produced scatters. The organiser's photos sit in a folder, the fan's clips sit on their camera roll, and within a week there is nothing left to point at. Drop Highlight builds the layer that holds it: a gallery for every event, published by the organiser, opened and added to by the people who were there. This is a look at what that could be inside DICE: bringing fans back into the app after an event, closer to the artists and venues behind it, and making the next ticket an easier ask.
This is a high-level initial ideas document rather than a proposal, shared to see whether there is synergy here. It remains confidential.
The Idea
Closing the loop.
For most events, the relationship ends at the door. Everyone there captures something, and most of it ends up in a story that expires in a day or a camera roll nobody else sees, almost never in anything attached to the event it came from. The organiser has content they have already paid for and no lasting surface to publish it on. And the platform that sold the ticket plays no part in any of it.
At present, every ticket a fan buys through DICE stays in their account long after the event. The event itself doesn't. We are open to exploring a partnership where it does: a gallery attached to each DICE event, appearing on the fan's own past-events screen, looking and behaving like a DICE feature.
Drop Highlight already builds and runs all of it, the gallery, the uploads, the review and the moderation, meaning this could be a relatively small lift for your team, while giving fans a reason to come back and partners a reason to stay.
What It Could Do
Two audiences, two different kinds of value.
The case for DICE runs on two fronts: what galleries add inside the app, and what it lets DICE offer its partners.
In the appDICE's own consumer product
01
The gap between one ticket and the next
Once an event is over there is usually nothing to bring a fan back until they want another ticket. A gallery fills that gap with a reason to open the app in the days that follow, while it is all still recent, and creates a visit there would otherwise be no reason to make.
02
Reaching fans at their warmest
A fan in a gallery is going back to something they chose to be at and enjoying it a second time. What is on next, put in front of someone in that state, reaches a far warmer audience than the same listing does anywhere else, and a follow won here carries into everything they are sold afterwards.
For partnersWhat DICE could offer them
03
Something to win business with
Most organisers pay for photography and video, use a handful of frames on social, and leave the rest gathering dust in a shared folder. A gallery on every event gives that content a permanent home, gives a ticketing pitch something to say beyond fees and reach, and gives a partner a reason to stay.
04
Fan content, captured and cleared
Attendees capture some of the most authentic shots from an event, and almost none get used because nobody holds the rights or the moderation to publish them safely. With Drop Highlight, permission is captured at upload and reviewed before it appears, so organisers can publish their fans' work and credit them for it.
The Fan Experience
How this could look for a fan.
From the prompt after an event through to a way back into DICE. The label above each screen says whose surface it is.
DICEScreens DICE ownsBuilt by your team, in your components and styling.
Drop HighlightScreens we serveRendered inside your app, themed to match.
DICE
Sunday 14 June
09:41
DICEnow
Sónar 2026 · add your photos
People who were there are adding theirs. Add yours and be part of the story.
The prompt comes from DICE. Sent under your own relationship with the fan.
Drop Highlight · in your app
09:41
Sónar 2026
Sónar 2026 · Friday
Your photos, your videos, your weekend. Add what you shot to the shared gallery to become part of the story.
214 people have added theirs
Your details
Full name
Email address
@instagram (optional)
Add your photos
Powered by Drop Highlight
Fan content is collected while the event is still fresh.
DICE
10:51
Events you went to
Sónar 2026 · Friday
Fira Montjuïc
Last month
Gallery Day Pass
2
Drumcode · Mallorca
Son Fusteret
Last year
Gallery Regular Ticket
4
Mochakk
Razzmatazz
The events a fan already has in their account, with a marker on the ones that have something behind them.
DICE
10:51
Sónar 2026 · Friday
Fira Montjuïc
Last month
2
Your tickets
2 x Day Pass
Gallery247 items
Photos and video from the event, plus what other people there shared.
Open gallery
This card is the main integration. On your side it can be as little as a container and a link.
Drop Highlight · in your app
09:41
Sónar 2026
Sónar 2026 · Friday
Shared by Sónar · 247 photos and videos
AllPhotosVideos
Add your photos
Powered by Drop Highlight
The gallery opens inside the app. No browser, no address bar, your back button.
Drop Highlight · in your app
24 of 100
Lucia Mati
@mati.lucia
From fans
DownloadShare
Every item credits whoever shared it, and carries a route for anyone to report something that shouldn't be there.
Drop Highlight · in your app
End of gallery
More from Sónar
Sónar 2026 · Saturday
13 Jun · 214 items
Sónar 2026 · Sunday
14 Jun · 237 items
Sónar 2025
Last year · 340 items
What's on at Sónar
Follow Sónar on DICE
The gallery ends on what comes next. A follow asked here reaches someone who has just spent time back at the event.
DICE
09:48
Sónar 2027
Fira Montjuïc, Barcelona · 17 to 19 Jun 2027
You came from the Sónar 2026 gallery
Electronic3 days18+
From
€185.00
Get tickets
A ticket page reached from a gallery rather than a listing. Sales that arrive this way can be attributed to it.
The Partner Experience
What the partner actually does.
Galleries need somewhere to live, so each partner would have a Drop Highlight account behind the scenes: a simplified version of the platform, built around the events they run with DICE, with little to learn beyond publishing a gallery.
A gallery would be created from the DICE event itself, so the partner opens something that is already set up. The event, the venue and the date arrive with it and stay tied to it. What they add is the content.
Every fan submission lands in a review queue that the partner works through, in Drop Highlight, reached from their own dashboard. Nothing publishes automatically. Approved files become gallery media, rejected ones are discarded, and every item carries a record of who submitted it and what they agreed to.
The content is the partner's: they review it, they can download all of it, and it lives on our infrastructure. Nothing about moderation or content management needs building into your partner tooling, and DICE would take on no storage, no transcoding, no moderation queue and no take-down obligation.
The Integration Roadmap
A phased approach, starting small.
The eventual shape of this would depend on how DICE's own systems are put together and on the resource available. We would suggest starting with the smallest build that works, then going deeper as the numbers justify it. Every route out of a gallery, to a follow, to an event page, to a checkout, can carry attribution, so the first events to run would show what those numbers look like for a DICE audience.
Phase oneThe smallest version that works
It starts with the partner
The partner sets the gallery up with us and ties it to their DICE event. Nothing is pushed between systems and none of this step needs anything from you. How they reach us, whether from MIO or elsewhere, would be a decision to make together.
One card in your app
A preview of the gallery on the past event screen: a panel we serve and maintain, a web view inside your own. The work on your side is a container and a link, placed once rather than per event. Where there is no gallery it renders nothing and the card is not there.
The gallery opens full screen
Tapping the card opens the gallery full screen. The screen and its back button are yours, and what renders inside is ours, styled with your typeface and colours. No browser, no address bar, and everything behind it stays with us.
Phase twoOnce it is working and worth the time
The card in your own components
The same content delivered through an API and rendered natively by your team, built from your own components so it moves with your design system. The card can then sit wherever you want it, on the event screen or anywhere else in the app.
A DICE-owned domain
The gallery moves from our domain to a DICE-owned subdomain pointed at our infrastructure, something like gallery.dice.fm, so shared links open in the app rather than a browser. Closer to configuration than engineering, and every shared link carries your name.
Turning it on from MIO
A switch inside MIO could provision the account outright, and events could flow through automatically, so a gallery is ready without anyone creating one. It reads as a DICE feature being enabled rather than a place to go.
The Commercials
More than one structure could work here.
The fan-facing surfaces above sit inside DICE and read as DICE. Behind them, our costs are storage, transcoding and delivery, and they scale with the size of an event. Whether that sits with DICE or with the partners themselves shapes everything else.
The structure could take more than one shape: a platform fee, a licence per event, a per-account arrangement, or some combination. Any of them can work, and which one makes sense would likely depend on scale and on how it would be positioned to partners.
DICE knows ticketing. Drop Highlight knows post-event content. Together we could close the loop on the event lifecycle for fans and partners alike, turning the end of one event into the start of the next.
Drop Highlight × DICE
Screens are indicative wireframes. Nothing here is a proposal or a commitment, and it remains confidential.
