I’ve been working with React since 2016 and still there isn’t a single best practice when it comes to application structure and design.
While there are best practices on the micro level, most teams build their own “thing” when it comes to architecture.
Of course, there isn’t a universal best practice that can be applied to all businesses and applications. But there are some general rules that we can follow to build a productive codebase.
The purpose of a software’s architecture and design is to keep it productive and flexible. Developers need to work on it effectively and modify it without rewriting its core.
This article is a collection of principles and rules that have proven to be effective for me and the teams I’ve worked with.
I outline good practices about components, application structure, testing, styling, state management and data fetching. Some of the examples are oversimplified so we can focus on the principle not on the implementation.
Take everything here as an opinion, not an absolute. There’s more than one way to build software.