How to use Reusable with UITableView in Swift?

Conform your cell class to Reusable or NibReusable, register it with tableView.register(cellType:), and dequeue using tableView.dequeueReusableCell(for: indexPath). This ensures type safety without string identifiers.

Reusable vs manual cell registration – which is better?

Reusable is better for type safety and reduced boilerplate, eliminating string-based errors. Manual registration offers more control for highly custom or legacy setups but requires more code and error-prone identifiers.

Can Reusable be used with SwiftUI?

No, Reusable is designed for UIKit and iOS development. SwiftUI handles view reuse declaratively without identifiers, so Reusable's patterns don't apply directly.

How to load a custom UIView from XIB using Reusable?

Conform your UIView to NibLoadable or NibOwnerLoadable, then call loadFromNib() for instantiation. For NibOwnerLoadable, override init(coder:) to auto-load content when used in Storyboards.

What are common errors when using Reusable and how to fix them?

Common errors include mismatched reuseIdentifiers or missing nib files. Reusable provides descriptive fatalError messages; check that identifiers in XIBs match class names and that cells are registered properly.

Is Reusable compatible with CocoaPods and SPM?

Yes, Reusable supports installation via CocoaPods, Carthage, and Swift Package Manager, with detailed instructions in the README for each dependency manager.

How to instantiate a UIViewController from storyboard with Reusable?

Conform your UIViewController to StoryboardBased or StoryboardSceneBased, then call instantiate() on the class. This automatically loads from the associated storyboard without string identifiers.

Reusable — Swift Mixin for View Reuse

What is Reusable?

Reusable is a Swift library that provides mixins for type-safe reuse of UI components in iOS apps, including UITableViewCells, UICollectionViewCells, custom UIViews, and UIViewController storyboards. It eliminates the need for string-based reuseIdentifiers, reducing boilerplate and potential runtime errors by leveraging Swift's type system.

Target Audience

iOS developers building apps with UIKit who want to simplify and secure the reuse of table view cells, collection view cells, and other UI components with compile-time safety.

Value Proposition

Developers choose Reusable for its elegant, protocol-based approach that removes string manipulation, provides clear error messages for misconfigurations, and integrates seamlessly with existing iOS conventions without requiring extensive code changes.

A Swift mixin for reusing views easily and in a type-safe way (UITableViewCells, UICollectionViewCells, custom UIViews, ViewControllers, Storyboards…)

Use Cases

Best For

Simplifying UITableViewCell and UICollectionViewCell registration and dequeuing
Loading custom UIViews from XIB files with type safety
Instantiating UIViewController from storyboards without string identifiers
Reducing boilerplate code in iOS view reuse patterns
Ensuring compile-time safety for reusable UI components
Adopting mixin-based design over inheritance in Swift projects

Not Ideal For

Projects using SwiftUI where view reuse is handled declaratively without identifiers
Teams heavily invested in string-based identifiers for legacy code or third-party library compatibility
Apps with highly dynamic cell types that change at runtime and don't benefit from compile-time type safety
Developers who prefer inheritance-based architectures over protocol mixins for UI design

Pros & Cons

Pros

Type-Safe Cell Reuse

Eliminates string-based reuseIdentifiers by using protocols like Reusable and NibReusable, ensuring compile-time safety and reducing errors, as shown in the dequeue examples without manual identifier manipulation.

Easy XIB Integration

Provides NibLoadable and NibOwnerLoadable protocols for loading custom UIViews from XIBs with simple calls like loadFromNib(), streamlining view instantiation.

Minimal Boilerplate

Conforming to protocols such as Reusable requires no additional code due to default mixin implementations, reducing repetitive registration and dequeuing logic.

Clear Error Messages

Uses descriptive fatalError messages for misconfigurations, like incorrect reuseIdentifiers, helping developers debug issues early, as mentioned in the README's error handling section.

Cons

UIKit and iOS Exclusive

Tied to UIKit and iOS development, making it unsuitable for projects using SwiftUI or targeting other Apple platforms without significant adjustments.

Requires Final Classes

Recommends marking subclasses as final for compiler optimizations, which can limit inheritance and flexibility in some architectural designs, as noted in the additional tips.

Convention-Driven Limitations

Relies heavily on naming conventions for reuseIdentifiers and nib files; deviations require custom implementations, adding complexity for non-standard use cases.

Swift Version Dependencies

Has specific version requirements for different Swift versions, as shown in the installation table, which could complicate upgrades or cross-version compatibility.

Frequently Asked Questions

What is Reusable?

Target Audience

iOS developers building apps with UIKit who want to simplify and secure the reuse of table view cells, collection view cells, and other UI components with compile-time safety.

Value Proposition

Use Cases

Best For

Simplifying UITableViewCell and UICollectionViewCell registration and dequeuing
Loading custom UIViews from XIB files with type safety
Instantiating UIViewController from storyboards without string identifiers
Reducing boilerplate code in iOS view reuse patterns
Ensuring compile-time safety for reusable UI components
Adopting mixin-based design over inheritance in Swift projects

Not Ideal For

Projects using SwiftUI where view reuse is handled declaratively without identifiers
Teams heavily invested in string-based identifiers for legacy code or third-party library compatibility
Apps with highly dynamic cell types that change at runtime and don't benefit from compile-time type safety
Developers who prefer inheritance-based architectures over protocol mixins for UI design

Pros & Cons

Pros

Type-Safe Cell Reuse

Easy XIB Integration

Provides NibLoadable and NibOwnerLoadable protocols for loading custom UIViews from XIBs with simple calls like loadFromNib(), streamlining view instantiation.

Minimal Boilerplate

Conforming to protocols such as Reusable requires no additional code due to default mixin implementations, reducing repetitive registration and dequeuing logic.

Clear Error Messages

Uses descriptive fatalError messages for misconfigurations, like incorrect reuseIdentifiers, helping developers debug issues early, as mentioned in the README's error handling section.

Cons

UIKit and iOS Exclusive

Tied to UIKit and iOS development, making it unsuitable for projects using SwiftUI or targeting other Apple platforms without significant adjustments.

Requires Final Classes

Recommends marking subclasses as final for compiler optimizations, which can limit inheritance and flexibility in some architectural designs, as noted in the additional tips.

Convention-Driven Limitations

Relies heavily on naming conventions for reuseIdentifiers and nib files; deviations require custom implementations, adding complexity for non-standard use cases.

Swift Version Dependencies

Has specific version requirements for different Swift versions, as shown in the installation table, which could complicate upgrades or cross-version compatibility.

Frequently Asked Questions

Reusable

What is Reusable?

Overview

Use Cases

Best For

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions

Related Projects

Found a gem we're missing?

Reusable

What is Reusable?

Overview

Use Cases

Best For

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions

Related Projects

Found a gem we're missing?