Error handling architecture: clean, rapid, reactive approach
summary
Describes a centralized, pluggable error-handling layer for mobile apps using Rx/Flow patterns: a base ErrorHandler class that presenters inherit, binds to lifecycle, and unpacks CompositeException. Validation is moved into use-case validation so presenters only handle happy paths, and the implementation unifies local cache/server merge and token-refresh logic, removes duplicated error code (cutting ~1000 lines) and speeds new-developer onboarding from ~1 month to ~1 week.
AI-written summary · about
chapters (12)
- 0:00Introduction
- 3:38Clean architecture basics
- 8:07Error handling problems
- 11:44UI error handler
- 16:07Error handler interface
- 20:02Error handling levels
- 23:12Use case validation
- 26:47Architecture benefits
- 30:22Implementation challenges
- 37:21Q&A
- 42:26Q&A
- 46:18Summary
related talks
31mHow Many Ways to Say I'm Sorry, Error Handling in React
17mA closer look into error handling techniques
32mError handling: doing it right!
46mSystematically handling errors in your code to make them useful
32mWriting Better Errors
44mInitiatory Journey from Exceptions to Composable Error Types
45mThe design of error
28mError handling: doing it right!