Accept stacked alerts or build a custom queue: which approach suits rapid error handling in Ionic?

Trade‑off: stacked alerts vs custom queue for Ionic AlertController

Goal: prevent notification noise when multiple error alerts are triggered in quick succession, such as from rapid HTTP failures.

Constraint: Ionic’s AlertController shows each alert immediately, causing a visual stack that users must dismiss one by one, while a custom queue service can enforce a single active alert but adds service logic, dismissal handling, and cleanup concerns.

Uncertainty: developers must weigh user experience clarity against implementation overhead, potential memory leaks, and interaction with navigation or backdrop dismissal.

What are the UX drawbacks of stacked alerts in rapid‑succession scenarios? How much extra code and testing does a reliable queue service require? Does managing a queue interfere with AlertController’s backdropDismiss or keyboardClose defaults?