Building software for a one-day global event
Lessons from pagination, time synchronization, responsive design, and maps on a live platform used by more than 1,000 people.
One Voice One Day was a 24-hour global digital gathering created by Firm Collective. I volunteered as a developer to help prepare its live platform, which was used by more than 1,000 people during the event.
Design around the event, not an average day
A live event creates a very different product constraint: the most important traffic arrives in a narrow window, and there is little room to repair the experience after that window passes.
That made responsiveness and predictable behavior essential. The platform needed to work across screen sizes while keeping chat, maps, and the shared schedule understandable.
Keep live interfaces bounded
I worked on pagination for the live chat so the interface did not try to handle an ever-growing message history all at once. A bounded view is easier for the browser to render and easier for a participant to navigate.
I also contributed to time synchronization. When people join from around the world, a shared event clock must be explicit and consistent rather than relying on each person to translate the schedule themselves.
Integrations need graceful edges
The Mapbox integration gave the gathering a sense of place, but third-party features also introduce loading and layout edge cases. The surrounding interface should remain useful even while an integration is catching up.
Small bug fixes and responsive adjustments often carry as much event-day value as a large new feature because they remove friction from the main journey.