A guide exploring why client-side web applications need a more structured architectural standard beyond MVC and MVP. The author argues that the 'model' in these patterns is too ambiguous, leading to confusion about which tools (Redux, React hooks, Apollo Client, etc.) handle which concerns. Drawing parallels to backend clean architecture with its domain, application, and infrastructure layers, the post makes the case for an equivalent layered approach on the frontend that balances testability, flexibility, and maintainability while preserving developer experience.
Table of contents
Why we need a client-side architecture standardWe need a shared language to talk about client-side architectureWe've already solved this problemClient-side needs — testability, flexibility, and maintainability1 Impression