Book Image

Hands-On Design Patterns with Swift

By : Florent Vilmart, Giordano Scalzo, Sergio De Simone
Book Image

Hands-On Design Patterns with Swift

By: Florent Vilmart, Giordano Scalzo, Sergio De Simone

Overview of this book

Swift keeps gaining traction not only amongst Apple developers but also as a server-side language. This book demonstrates how to apply design patterns and best practices in real-life situations, whether that's for new or already existing projects. You’ll begin with a quick refresher on Swift, the compiler, the standard library, and the foundation, followed by the Cocoa design patterns – the ones at the core of many cocoa libraries – to follow up with the creational, structural, and behavioral patterns as defined by the GoF. You'll get acquainted with application architecture, as well as the most popular architectural design patterns, such as MVC and MVVM, and learn to use them in the context of Swift. In addition, you’ll walk through dependency injection and functional reactive programming. Special emphasis will be given to techniques to handle concurrency, including callbacks, futures and promises, and reactive programming. These techniques will help you adopt a test-driven approach to your workflow in order to use Swift Package Manager and integrate the framework into the original code base, along with Unit and UI testing. By the end of the book, you'll be able to build applications that are scalable, faster, and easier to maintain.
Table of Contents (22 chapters)
Title Page
Copyright and Credits
About Packt
Contributors
Preface
Index

Summary


The MVC pattern should now hold no confusion for you. We have seen in this chapter how this design pattern is widely misunderstood on iOS, and often leads to Massive View Controller syndrome. Hopefully, you should now be able to refactor your code to improve the readability and maintainability of your view controllers, and properly isolate each layer.

We discussed how to use view controller composition with child view controllers, in order to reduce overly complex view controllers or views.

In a nutshell, you should always ensure view controllers only have view layout logic, and increase separation by focusing the responsibilities of each view controller as much as possible. Never forget you can create controllers, model controllers, or other pure objects to help hold your programs together while keeping your view controllers clean.

Following this recommendation should increase the quality of your code base if you're using the MVC pattern across your project.

In the next chapter, we...