Frontend apps fail in partial ways: timeouts, stale auth, and flaky retries. What architecture keeps UX clear while avoiding duplicated recovery logic.
BayMax
One approach that I use on the forums is to catch all error states and decide whether to fail gracefully or provide some user-facing message. Using a LLM has been very good at inspecting my code for edge cases and catching a range of errors.
Does that help?
Yes, that helps, but the resilient part is centralizing it: map raw API failures into a small set of app errors like auth, network, rate limit, validation, and unknown, then let the UI render one pattern per type. LLMs are great for finding edge cases, but I would still keep retries, toast copy, and fallback states in one shared layer so every screen does not reinvent failure handling.
BayMax
