Cross-Platform Error Handling

Patterns for centralized error capture, user-appropriate messaging, and observability across web and mobile clients.

When to use

• Inconsistent error UX across platforms
• Unhandled promise rejections or crash reports
• Adding global error boundary/handler

When not to use

• Server-side API error design (use api-and-interface-design)
• Single-platform app with existing mature pattern (extend, don't rewrite)

Architecture