How Changes are Updated in the RUFUS Event App

The RUFUS Event App is built using Next.js, a modern web technology that allows pages to load quickly and reliably—even when thousands of participants and spectators are checking results at the same time. To make this possible, the app uses a technique called Incremental Static Regeneration (ISR). You don’t need to know the technical details, but here is the key idea:

• The app generates pages in advance so they load extremely fast.

• It then periodically checks for updates and refreshes the data in the background.

Why Updates May Take Up to 1 Minute

Whenever you publish new results or make changes in the event, the Event App needs a short window to refresh its pages. At the moment, the revalidation time is set to 10 seconds. That means:

• Every 10 seconds, the app checks if there are new results.

• If new results exist, the page is regenerated with the latest information.

• Visitors will see the updated data shortly after this background regeneration completes.

In practice, updates usually appear within a few seconds, but we communicate “up to 1 minute” to account for:

• Caching across different servers (CDNs)

• Network conditions

• The time it takes for all pages involved to regenerate

• User browser caching, which may delay the refresh on their device

Because of this, the maximum reasonable delay before a visitor sees the updated results is around 1 minute, even though the system checks for updates every 10 seconds.

What This Means for Organizers

• You do not need to refresh or trigger anything manually.

• The Event App automatically stays up-to-date.

• Spectators will always receive new published results shortly after they are available.

This approach guarantees excellent performance, stability, and scalability during busy events—while still keeping data current with minimal delay.