CRESA Begins Tackling Multiple Alerts at Once

As CRESA's alert system becomes more capable, development reaches a problem every event-driven broadcast system eventually has to solve: what happens when several things happen at once? Work begins on a more advanced queue and presentation architecture capable of coordinating alerts rather than allowing multiple experiences to compete for the screen.

An animated queue stack is introduced, providing a way for incoming activity to remain visible and organised while another presentation is already underway. Compact alert presentation also begins evolving during this work, exploring ways for CRESA to acknowledge stream activity without every event requiring a large fullscreen interruption.

Considerable development goes into the runtime underneath it. Queue preservation, presentation arbitration and stack-safe behaviour are refined as CRESA learns how to transition between singular and stacked alert states without losing events or presenting them twice.

This proves to be a significantly more complicated problem than simply drawing several alerts on screen. The browser presentation, event queue and runtime all need to agree on who currently owns the presentation and what should happen next. Several iterations are made as the architecture is stabilised, including returning parts of the runtime to a simpler single-queue model where necessary before building forward again.

It's an early example of an important development philosophy for CRESA: reliability takes priority over keeping a more complicated design simply because it already exists. The work started here will eventually develop into CRESA's broader routing and presentation framework, including Single, Stacked and Quiet alert experiences.