Steps

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

results matching ""

    No results matching ""