We started off this chapter by looking at the Elm arhitecture: Model, View, and Update. We also mentioned another important ingredient: Messages, a way for Views to communicate with Updates.
We used a very simple example app, Fruit Counter. The app was simple indeed: the only message our view could ever send to the update function was Decrement. The simplicity of the app we made was a great way for us to understand the architecture without having to introduce too many concepts that would get in the way of learning.
However, now that we have a rudimentary understanding of all the moving parts and how they fit together, we can talk about another level of complexity related to messages in the Elm arhitecture.
To do that, ...