Discover and read the best of Twitter Threads about #clientsidearchitecture
Most recents (1)
Every client app uses some form of the MVP (model-view-presenter) pattern.
The challenge is that the M is responsible for way too much.
As a result, developers don't know *which tools* are responsible for which tasks.
The challenge is that the M is responsible for way too much.
As a result, developers don't know *which tools* are responsible for which tasks.
Tasks of the model:
- Providing reactivity to state changes
- Holding onto state
- Updating remote data and providing async states (loading, success, error)
- Expressing model behavior. Also known as domain (interaction) logic.
- Providing reactivity to state changes
- Holding onto state
- Updating remote data and providing async states (loading, success, error)
- Expressing model behavior. Also known as domain (interaction) logic.
Tools we can use:
- React hooks
- Redux
- Context API
- Apollo Client
- RESTful APIs
- xState
- react-query
- React hooks
- Redux
- Context API
- Apollo Client
- RESTful APIs
- xState
- react-query
