The MVC architecture provides us with a standard way of organizing our applications and means that the code can be easily read and understood by other developers because things are always in the same place.
After creating our application's views we must start handling events raised after a user interacts with them, and use our controller actions to provide a path through our application.
Before the MVC architecture existed, this interaction was usually dealt with inside the view itself, that is, a tight coupling between application logic and presentation definitions. MVC allows us to remove this coupling and let views solely focus on displaying data and have the controllers tie everything together.
In this recipe, we will demonstrate how to listen for user interactions on our views and have the controller deal with the logic needed to move the user through our application.