Question 1

How to implement conditional screen flows with SwiftCurrent?

Accepted Answer

Use the shouldLoad() method in FlowRepresentable views to conditionally skip screens, and compose workflows for branching logic, as shown in the quick start example with OptionalView.

Question 2

SwiftCurrent vs native SwiftUI navigation: which is better?

Accepted Answer

SwiftCurrent excels at complex, conditional workflows with compile-time safety, while native SwiftUI navigation is simpler for basic linear flows; choose based on your app's navigation complexity.

Question 3

Can SwiftCurrent handle authentication flows?

Accepted Answer

Yes, by composing workflows and using conditional logic, you can create robust authentication sequences that adapt based on user state, leveraging the library's support for branching flows.

Question 4

How to pass data between screens in SwiftCurrent?

Accepted Answer

Data is passed through the init(with:) method of FlowRepresentable views, ensuring type safety and clear data flow, as demonstrated in the quick start with input arguments.

Question 5

Does SwiftCurrent work with Swift Concurrency (async/await)?

Accepted Answer

The README doesn't specify, but since it's Swift-based, integration with concurrency would require custom implementation; it's not a built-in feature of the library.

Question 6

What are the performance costs of using SwiftCurrent?

Accepted Answer

Minimal overhead due to compile-time optimizations, but for server-driven workflows with dynamic decoding, there might be runtime performance implications depending on data size.

SwiftCurrent

What is SwiftCurrent?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions