Product decisions4 min read

Why Festivalio became a multi-edition platform instead of a single-event companion

The product and architectural decisions behind evolving Festivalio from an Ozora 2026 companion into an offline-first, multi-edition festival platform.

The starting point

Festivalio began as a single-purpose tool: an interactive timetable and personal schedule companion for Ozora 2026. The entire data model, UI structure, and offline caching strategy were built around one festival, one year, one set of stages.

When the festival ended, the product had proven its core value — an offline-first PWA, schedule coordination without accounts, and an immersive visual design tuned to the festival atmosphere. But the architecture assumed “one festival, one edition” at every level.

The decision

Rather than archive the codebase and start fresh for the next edition, we chose to restructure Festivalio as a multi-edition platform. The reasoning: the core utility — timetable navigation, personal scheduling, offline access, stage wayfinding — is edition-independent. What changes between editions is the data, the visual theme, and some festival-specific configuration.

What changed

Three architectural layers had to shift:

  1. Data loading became dynamic. Edition-specific timetable, lineup, and map data load based on a selected edition, rather than being hardcoded into the build.
  2. State scoping. Favorites, notes, priorities, and campsite data now scope to the edition they were created in. A 2026 schedule doesn’t bleed into 2027.
  3. Brand and domain. Festivalio received its own domain at festivalio.bersaglio.work and an endorsed product status under Bersaglio, with dedicated support and feedback channels.

An edition switcher lets users navigate between the 2026 archive and the 2027 preparation hub within the same interface.

What we learned

The hardest part wasn’t the technical restructuring — it was defining what an “edition” means in the data model. A festival edition isn’t just a year label; it’s a complete dataset (stages, artists, times, map) that needs to be self-contained while sharing the same UI shell. Getting that boundary right took more iteration than the actual code changes.

What’s next

Festivalio is now positioned as a multi-festival, multi-year platform. The immediate next steps are supporting the 2027 edition with real data as it becomes available, and exploring user accounts for cross-device schedule sync.

Follow on Google Search

Add Bersaglio as a preferred source to prioritize our notes, research, and product insights in Search and AI Overviews.

Accessibility options

Customize display preferences. These controls do not replace accessible site markup or assistive technology testing.