iOS apps are often developed using a design pattern called Model-View-Controller (MVC). In this pattern, each class, struct, or enum is either a model object, view, or a controller. Model objects are responsible for storing data. They should be independent of the kind of presentation by the UI. For example, it should be possible to use the same model object for an iOS app and a command-line tool on macOS.

View objects are the presenters of the data. They are responsible for making the objects visible (or hearable in the case of a VoiceOver-enabled app) for the user. Views are special for the device that the app is executed on. In the case of a cross-platform application, view objects cannot be shared. Each platform needs its own implementation of a view layer.

Controller objects communicate between the model and view objects. They are responsible for making the model objects presentable.

We will use MVC for our to-do app because it is one of the easiest design patterns, and it is commonly used by Apple in its sample code.

This chapter starts our journey in the field of TDD with the model layer of our application. It is divided into three sections:

• Implementing the ToDoItem struct
• Implementing the Location struct
• Implementing the ItemManager class