#24 - iOS Structural Patterns
How to deal with object structures
Hey iOS developer! 👋
Last week, I began exploring iOS design patterns, starting with creational patterns.
In today's issue, I'll continue by diving into six iOS structural patterns: Adapter, Bridge, Composite, Facade, Flyweight, and Proxy.
Adapter Design Pattern in iOS
The Adapter pattern enables incompatible interfaces to collaborate without modifications. By creating an 'adapter' class, one object is transformed to align with another's interface, facilitating seamless integration. This approach is particularly beneficial when incorporating third-party libraries or updating legacy code to function with new APIs.
For an in-depth exploration of the Adapter pattern, consider reading Omar Saibaa's article.
Read on Medium
The Bridge Pattern in Swift: A Comprehensive Guide
In the next article, we’ll explore the pros and cons of the Bridge pattern. This pattern decouples an abstraction from its implementation, allowing each to evolve independently. With this approach, we define a common protocol (the abstraction) and create multiple classes to implement that protocol with specific functionality (the implementations). The bridge class acts as the link between the abstraction and its implementations, holding a reference to any implementation class.
This design provides flexibility, making it easy to switch between implementations without modifying the abstraction.
Read on Medium
Composite Design Pattern in iOS
According to the next pattern—Composite—we organize objects hierarchically so that single objects and groups can be managed seamlessly. The Composite pattern defines a shared protocol (the component), which allows individual elements (leaves) and their collections (composites) to work together in a unified structure.
The best part of the selected article is how the Abdul Ahad first defines the problem, then presents the solution using the Composite pattern, and explains how this approach effectively resolves the issue.
Read on Medium
Curated iOS newsletter is now published twice a week.
In addition to the traditional Wednesday issues, I’m sending out Monday emails with a series of personal articles called Monday Quick Read.This week, I talked about how to stay on top of things as a non-indie developer with the constant new OS releases.
Facade Design Pattern in iOS
The Facade design pattern solves the problem of simplifying interaction with complex systems by hiding implementation details under a unified interface.
Check out another great article by Omar Saibaa on the Facade pattern.
Read on Medium
Flyweight Design Pattern in iOS
The Flyweight pattern aims to reduce memory usage by sharing common data across similar objects. Instead of creating separate instances for each object, it reuses existing ones and stores only the unique data specific to each object. This approach allows for efficient memory management, especially when handling a large number of similar objects.
Check out this article by Jaime Escobar.
Read on Medium
The Proxy Pattern in Swift: A Comprehensive Guide
The Proxy pattern introduces an object that represents another object, essentially acting as a placeholder that controls access to the actual object with added functionality, such as access control, logging, or lazy initialization.
Here is the final article in this issue.
Read on Medium
If you’ve enjoyed this article, I’d be happy if you:
Hit the Like button.
Subscribe, if you haven’t already!
Connect with me on LinkedIn.
Share the issue with colleagues or friends who might find it helpful.
Until next time!
Artjoms