Packt+ | Advance your knowledge in tech

You're reading from Hands-On Design Patterns with Swift Master Swift best practices to build modular applications for mobile, desktop, and server platforms

Product type Paperback

Published in Dec 2018

Publisher Packt

ISBN-13 9781789135565

Length 414 pages

Edition 1st Edition

Languages

Swift

Tools

Foundation

Concepts

Design Patterns

Authors (3):

Giordano Scalzo

Florent Vilmart

Sergio De Simone

View More author details

Table of Contents (17) Chapters

Preface

1. Refreshing the Basics

2. Understanding ARC and Memory Management FREE CHAPTER

3. Diving into Foundation and the Standard Library

4. Working with Objective-C in a Mixed Code Base

5. Creational Patterns

6. Structural Patterns

7. Behavioral Patterns

8. Swift-Oriented Patterns

9. Using the Model-View-Controller Pattern

10. Model-View-ViewModel in Swift

11. Implementing Dependency Injection

12. Futures, Promises, and Reactive Programming

13. Modularize Your Apps with Swift Package Manager

14. Testing Your Code with Unit and UI Tests

15. Going Out in the Open (Source)

16. Other Books You May Enjoy

Leave a review - let other readers know what you think

A refresher on MVC

MVC is a design pattern that encourages separation of concerns. It was invented in 1978, and was generalized in the 80s. Smalltalk was the first language to make extensive use of this design pattern for the creation of user interfaces.

Objective-C, being heavily influenced by Smalltalk, then inherited this design pattern. AppKit and UIKit are also built around it.

While one could argue that other patterns can be just as efficient (or more so), MVC has the benefit of being widely understood by many developers, independent of their language of choice. MVC is widely used and is available in all object-oriented languages.

The theory behind the MVC pattern

Let's go back to the original description of the design pattern:

Model classes are used to represent knowledge and data. A model can be represented as a single object or structures.
View classes are used to represent the data to the user.
Controller classes are used to validate input from the user, passing it to the model layer...