Is Typhoon still maintained in 2024?

Typhoon's development has slowed with the introduction of Pilgrim as its Swift successor; while it's stable for Objective-C, active updates are limited, so check the GitHub repository for recent activity.

How do I integrate Typhoon with a SwiftUI project?

Typhoon can be used via dynamic frameworks in Swift, but it's not optimized for SwiftUI; you'll need to bridge Objective-C code and may find Pilgrim or other Swift-native DI frameworks more suitable.

Typhoon vs Swinject for iOS dependency injection?

Typhoon excels in Objective-C with runtime automation, while Swinject is Swift-native and more modern for Swift projects; choose based on your codebase language and maintenance needs.

Can Typhoon handle circular dependencies?

Yes, Typhoon supports circular dependencies through its runtime injection, but configuration can become complex; refer to the user guide for best practices and examples.

What are the performance impacts of using Typhoon?

Runtime injection adds overhead during object instantiation, which might affect startup time in large apps; profile your application to ensure it meets performance requirements.

How to migrate from Typhoon to Pilgrim?

The README provides a migration path; start by replacing Typhoon assemblies with Pilgrim's Swift-native setup, and use the documentation for step-by-step guidance.

Open-Awesome

Typhoon

Apache-2.0Objective-C4.0.9

A powerful, lightweight dependency injection framework for Objective-C and Cocoa applications.

Visit Website GitHub

2.7k stars260 forks0 contributors

What is Typhoon?

Typhoon is a dependency injection framework for Objective-C and Cocoa/CocoaTouch applications. It helps developers manage object dependencies and improve testability by providing a structured way to wire components together. The framework uses the Objective-C runtime to automate instantiation and injection, reducing boilerplate code.

Target Audience

Objective-C developers building iOS or macOS applications who need a robust, lightweight dependency injection solution. It's also suitable for teams maintaining legacy Objective-C codebases or integrating with Swift projects.

Value Proposition

Typhoon stands out for its runtime-based approach, which simplifies configuration and reduces manual wiring. It's lightweight yet full-featured, offering a balance of power and ease of use that's tailored specifically for the Cocoa ecosystem.

Overview

Powerful dependency injection for Objective-C ✨✨ (https://github.com/appsquickly/pilgrim is the pure Swift successor to Typhoon!!)✨✨

Use Cases

Best For

Managing complex object graphs in large Objective-C applications
Improving testability and modularity in iOS/macOS projects
Reducing boilerplate code for dependency management
Integrating dependency injection into legacy Objective-C codebases
Supporting Swift interoperability via dynamic frameworks
Structuring Cocoa applications with clear separation of concerns

Not Ideal For

Modern Swift-only applications seeking native dependency injection
Projects requiring active framework updates and Swift 5+ optimization
Teams avoiding Objective-C runtime overhead for performance or security reasons
Simple apps where manual dependency management suffices without added complexity

Pros & Cons

Pros

Runtime Automation

Uses Objective-C runtime metadata to automatically instantiate and wire objects, reducing manual configuration and boilerplate code as highlighted in the README.

Lightweight Integration

Supports CocoaPods, Carthage, and manual source integration, making it easy to add to existing Cocoa projects without bloat.

Broad Compatibility

Works with iOS 5+, OS X 10.7+, and dynamic frameworks for Swift interoperability, ensuring support for legacy and mixed codebases.

Community Documentation

Backed by extensive documentation, sample apps, and active Stack Overflow support, providing resources for learning and troubleshooting.

Cons

Limited Swift Support

The README explicitly states Typhoon is not great for modern Swift and recommends Pilgrim as the successor, making it suboptimal for Swift-focused development.

Aging Codebase

With copyright up to 2015 and a successor framework announced, Typhoon may have reduced active maintenance and fewer updates for newer iOS versions.

Runtime Dependency Overhead

Relies on Objective-C runtime manipulation, which can introduce performance overhead and complexity in pure Swift or performance-critical applications.

Frequently Asked Questions

Related Projects

Swinject

Dependency injection framework for Swift with iOS/macOS/Linux

Stars6,704

Forks542

Last commit10 months ago

Needle

Compile-time safe Swift dependency injection framework

Stars2,010

Forks162

Last commit2 months ago

Cleanse

Lightweight Swift Dependency Injection Framework

Stars1,770

Forks82

Last commit2 years ago

Dip

Simple Swift Dependency container. Use protocols to resolve your dependencies and avoid singletons / sharedInstances!

Stars980

Forks71