Steps
- Give a glimpse to wireframe provided by designer
- Identify the screen flow
- Identify data source
- Identity user story
- Based on user story, split the whole application into flows / intentions / scenes / story that
- A set of pages / views are designed for a purpose
- These pages are likely to reuse similar data source
- These pages are likely to have a predefined flow, in OOP word, we call it lifecycle or state machine
- If a portfolio consists of multiple projects, balance the divisions on top of individual interest
- For each flows / intentions / scenes / story
- Draft one
reducer structure such that selectors could make use of minimal data to produce information
- Draft a set of
actions such that reducer functions could mainly divided into initial and accumulative
- Assemble
selectors to single selector for single container using reselect
- Compose
containers that connecting one selector and all actions
- Draft a set of
sagas for each action
- Draft a set of
services used by sagas
- Get ready your SDK by
- Merge all reducers to rootReducer
- Merge all saga to rootSaga
- Export all containers
- Iterate these steps until the end of project
- Implement the business logic of
reducer, selector, action, container, saga
- Identify the
service and write an enhancer for the service required
- Implement and connect
presenter
- Implement
routes
- Optionally use
config