With more traditional frontend architectures, models that map directly to what's returned from the API provide a clear and concise data model for our JavaScript components to work with. Flux, as we now know, leans more in the direction of the user, and focuses on the information that they need to see and interact with. This doesn't need to be a gigantic headache for us, especially if we're able to decompose our user interface into domains. Think of a domain as a really big feature.
In this section, we'll talk about identifying the top-level features that form the core of our UI. Then, we'll work on shedding irrelevant API data from the equation. We'll finish the section with a look at the structure of our store data, and the role it plays in the design of our skeleton architecture.