Search Results for "pattern"

Swinject is a lightweight dependency injection framework for Swift. Dependency injection (DI) is a software design pattern that implements Inversion of Control (IoC) for resolving dependencies. In the pattern, Swinject helps your app split into loosely-coupled components, which can be developed, tested, and maintained more easily. Swinject is powered by the Swift generic type system and first-class functions to define the dependencies of your app simply and fluently.

Design-Patterns-In-Swift is a repository that translates classic software engineering design patterns (from sources like the Gang of Four) into Swift code examples, so you can see how those patterns look in a modern, strongly typed, object-/protocol-oriented language. It covers creational, structural, and behavioral patterns: singletons, factories, decorators, observers, strategy, command, mediator, and more. For each pattern, you’ll typically see one or more Swift implementations, commentary on where it makes sense in a Swift architecture, and caveats about when you might prefer pure protocol composition or using functional patterns instead. The examples aim to be readable and idiomatic—not overly abstract or contrived—so developers can adopt or adapt them directly.

Dollar is a Swift library that provides useful functional programming helper methods without extending any built in objects. It is similar to Lo-Dash or Underscore.js in Javascript. Cent is a library that extends certain Swift object types using the extension feature and gives its two cents to Swift language. It is now moved into a separate repo to support Swift Package Manager.

...It offers a good public API with out-of-box implementations and great customization possibilities. Cache utilizes Codable in Swift 4 to perform serialization. The cache is built based on a Chain-of-responsibility pattern, in which there are many processing objects, each knows how to do 1 task and delegates to the next one, so can you compose Storage the way you like. All Storage now are generic by default, so you can get a type of safety experience. Once you create a Storage, it has a type constraint that you don't need to specify a type for each operation afterward.

...Unlike traditional static PNG images, APNG supports frame-by-frame animation with full-color images and transparency — yielding better visual fidelity than GIFs while remaining efficient. APNGKit offers a friendly API (e.g. APNGImage, APNGImageView) that behaves similarly to the standard image/image-view pattern, making it easy for iOS/macOS developers to adopt without learning complex new APIs. It handles loading, decoding, timing, and rendering of animated PNG frames, providing smooth animations, correct color and transparency handling, and performance optimizations. The library supports modern Apple platforms (iOS, macOS, tvOS, visionOS) and works with standard dependency managers (Swift Package Manager, CocoaPods), making integration into existing projects straightforward.

Powerful navigation library for iOS based on the coordinator pattern. Create an enum with all of the navigation paths for a particular flow, i.e. a group of closely connected scenes. (It is up to you when to create a Route/Coordinator. As our rule of thumb, create a new Route/Coordinator whenever a new root view controller, e.g. a new navigation controller or a tab bar controller, is needed.). Whereas the Route describes which routes can be triggered in a flow, the Coordinator is responsible for the preparation of transitions based on routes being triggered. ...

LeeGo is a lightweight Swift framework that helps you decouple & modularise your UI component into small pieces of LEGO-style's bricks, to make UI development declarative, configurable and highly reusable. We all know that MVC pattern has some serious problems when dealing with a complex iOS project. Fortunately, there are also a bunch of approaches that aim to fix the problems, most of them mainly address the Controller part, such as MVP, MVVM, MVSM or VIPER. But there is barely a thing that addresses the View part. Does that mean we just run out of all the problems in the View part? ...