SwiftCurrent alternatives and similar libraries
Based on the "App Routing" category.
Alternatively, view SwiftCurrent alternatives based on common mentions on social networks and blogs.
-
RxFlow
RxFlow is a navigation framework for iOS applications based on a Reactive Flow Coordinator pattern -
RouteComposer
Protocol oriented, Cocoa UI abstractions based library that helps to handle view controllers composition, navigation and deep linking tasks in the iOS application. Can be used as the universal replacement for the Coordinator pattern. -
ZIKRouter
Interface-oriented router for discovering modules, and injecting dependencies with protocol in Objective-C and Swift. -
Composable Navigator
An open source library for building deep-linkable SwiftUI applications with composition, testing and ergonomics in mind -
DZURLRoute
DZURLRoute是支持基于标准URL进行Native页面间跳转的Objective-C实现。方便您架构页面之间高内聚低耦合的开发模式。他的核心思想是把每一个页面当成一个资源,通过标准的URL协议(统一资源定位符)来定位到每一个可触达的页面(资源)。 -
CoreNavigation
📱📲 Navigate between view controllers with ease. 💫 🔜 More stable version (written in Swift 5) coming soon. -
Weavy
DISCONTINUED. Reactive navigation framework based on a weaving pattern (fits well with RxSwift)
CodeRabbit: AI Code Reviews for Developers

Do you think we are missing an alternative of SwiftCurrent or a related project?
README
Welcome
SwiftCurrent is a library that lets you easily manage journeys through your Swift application and comes with built-in support for UIKit and SwiftUI app-routing.
Why Should I Use SwiftCurrent?
In SwiftCurrent, workflows are a sequence of operations. Those operations usually display views in an application. The workflow describes the sequence of views and manages which view should come next. Your views are responsible for performing necessary tasks before proceeding forward in the workflow, like processing user input.
Architectural patterns and libraries that attempt to create a separation between views and workflows already exist. However, SwiftCurrent is different. We took a new design approach that focuses on:
- A Developer-Friendly API. The library was built with developers in mind. It started with a group of developers talking about the code experience they desired. Then the library team took on whatever complexities were necessary to bring them that experience.
- Compile-Time Safety. At compile-time, we tell you everything we can so you know things will work.
- Minimal Boilerplate. We have hidden this as much as possible. We hate it as much as you do and are constantly working on cutting the cruft.
From There, We Created a Library
This library:
- Isolates Your Views. Design your views so that they are unaware of the view that will come next.
- Easily Reorders Views. Changing view order is as easy as ⌘+⌥+[ (moving the line up or down).
- Composes Workflows Together. Create branching flows easily by joining workflows together.
- Creates Conditional Flows. Make your flows robust and handle ever-changing designs. Need a screen to only to show up sometimes? Need a flow for person A and another for person B? We've got you covered.
Quick Start
Why show a quick start when we have an example app? Because it's so easy to get started, we can drop in two code snippets, and you're ready to go! This quick start uses Swift Package Manager and SwiftUI, but for other approaches, see our installation instructions.
.package(url: "https://github.com/wwt/SwiftCurrent.git", .upToNextMajor(from: "4.5.0")),
...
.product(name: "SwiftCurrent", package: "SwiftCurrent"),
.product(name: "SwiftCurrent_SwiftUI", package: "SwiftCurrent")
Then make your first FlowRepresentable view:
import SwiftCurrent
import SwiftUI
struct OptionalView: View, FlowRepresentable {
weak var _workflowPointer: AnyFlowRepresentable?
let input: String
init(with args: String) { input = args }
var body: some View { Text("Only shows up if no input") }
func shouldLoad() -> Bool { input.isEmpty }
}
struct ExampleView: View, PassthroughFlowRepresentable {
weak var _workflowPointer: AnyFlowRepresentable?
var body: some View { Text("This is ExampleView!") }
}
Then from your ContentView
or whatever view (or app) you'd like to contain the workflow, add the following view to the body:
import SwiftCurrent_SwiftUI
// ...
var body: some View {
// ... other view code (if any)
WorkflowView(launchingWith: "Skip optional screen") {
WorkflowItem(OptionalView.self)
WorkflowItem(ExampleView.self)
}
}
And just like that, you've got a workflow! You can now add more items to it or reorder the items that are there. To understand more of how this works, check out our developer docs.
Server Driven Workflows
SwiftCurrent now supports server driven workflows! Check out our schema for details on defining workflows with JSON, YAML, or any other key/value-based data format. Then, simply have your FlowRepresentable
types that you wish to decode conform to WorkflowDecodable
and decode the workflow. For more information, see our docs.
Look at Our Example Apps
We have example apps for both SwiftUI and UIKit that show SwiftCurrent in action. They've already been tested, so you can see what it's like to test SwiftCurrent code. To run it locally, start by cloning the repo, open SwiftCurrent.xcworkspace
and then run the SwiftUIExample
scheme or the UIKitExample
scheme.
Click Here to Learn More
For specific documentation check out:
- Why SwiftCurrent?
- Installation
- Getting Started With SwiftUI
- Getting Started With Storyboards
- Getting Started With Programmatic UIKit Views
- Server Driven Workflows
- Developer Documentation
- Upgrade Path
- Contributing to SwiftCurrent
Feedback
If you like what you've seen, consider giving us a star! If you don't, let us know how we can improve.
Special Thanks
SwiftCurrent would not be nearly as amazing without all of the great work done by the authors of our test dependencies:
*Note that all licence references and agreements mentioned in the SwiftCurrent README section above
are relevant to that project's source code only.