Question 1

How do I integrate XCoordinator with RxSwift in my app?

Accepted Answer

Install the 'XCoordinator/RxSwift' CocoaPods pod and use the router.rx.trigger extension to sequence transitions reactively. For example, you can chain routes with flatMap operators, as shown in the RxSwift extensions example where .home and .news routes are triggered sequentially.

Question 2

Can XCoordinator be used with SwiftUI projects?

Accepted Answer

No, XCoordinator is designed for UIKit-based navigation and does not natively support SwiftUI's declarative navigation system. It focuses on programmatic coordination with UIViewControllers, making it less suitable for pure SwiftUI apps.

Question 3

What's the difference between XCoordinator and manual UIKit navigation controllers?

Accepted Answer

XCoordinator abstracts navigation logic into coordinators with type-safe routes, reducing boilerplate and improving testability. In contrast, manual UIKit approaches often embed navigation code in view controllers, leading to tighter coupling and harder maintenance, as explained in the 'Why coordinators' section.

Question 4

How to handle memory leaks when using coordinators in XCoordinator?

Accepted Answer

Use the appropriate router abstractions: StrongRouter for child coordinators, WeakRouter or UnownedRouter for references in view models or view controllers. The README's 'When to use which Router abstraction' section details this to prevent retain cycles.

Question 5

What are best practices for splitting large routes in XCoordinator?

Accepted Answer

For huge routes, consider using RedirectionRouter to map new route types onto parent routes or create multiple coordinators with the same rootViewController. The README cautions that sibling coordinator transitions can cause crashes if not handled carefully.

Question 6

How does XCoordinator support custom animations for transitions?

Accepted Answer

You can define custom Animation objects with presentation and dismissal animations in the prepareTransition method. For instance, the Custom Transitions example shows how to specify YourAwesomePresentationTransitionAnimation for a push transition.

Question 7

Is XCoordinator good for testing navigation flows?

Accepted Answer

Yes, by decoupling navigation logic into coordinators, it allows unit testing of routes and transitions without involving view controllers. The framework's separation of concerns enables mocking routers to verify triggered routes, enhancing testability as highlighted in the value proposition.

RxCoordinator

What is RxCoordinator?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions