This chapter was about getting started with a Flux architecture by building some skeleton components. The goal being to think about the information architecture, without the distraction of other implementation issues. We could find ourselves in a situation where the API is already defined for us, or where the user experience is already in place. Either of these factors will influence the design of our stores, and ultimately the information we present to our users.
The stores we implemented were basic, loading data when the application starts and updating their state in response to an API call. We did, however, learn to ask the pertinent questions about our stores, such as the approach taken with parsing the new data to set as the store's state, and how this new state will affect other stores.
Then, we thought about the top-level features that form the core of our application. These features give a good indication of the stores that our architecture will need. Toward the end of the...