Swiftpack.co - Package - BottleRocketStudios/iOS-Scotty


CI Status Version Carthage compatible License Platform codecov codebeat badge


This library provides a simple abstraction around the various entry points to an iOS application. URLs, application shortcut items, user activities, notification responses, and even custom types can be converted into a Route. These routes represent the various destinations your app can deep link too, allowing you to have a single code path through which all application links are executed.

Key Concepts

  • Route - An abstract representation of the code required to move your application from its root state to a specific final destination.
  • RouteController - An object that is created with a root view controller, and handles the execution of Routes.
  • RouteAction - An action that can be taken by the destination of a Route when travel has completed.


An instance of the RouteController should be created and retained somewhere accessible by your Application Delegate so that the relevant callbacks can be forwarded on to it. Although the RouteController can be wrapped and treated as a singleton, it does not have to be.

class AppDelegate: UIResponder, UIApplicationDelegate {
    var routeController: RouteController<UITabBarController>?
    //In this implementation, our root view controller is a UITabBarController

    func application(_ application: UIApplication, didFinishLaunchingWithOptions launchOptions: [UIApplicationLaunchOptionsKey : Any]?) -> Bool {
        if let window = window, let rootVC = window.rootViewController as? UITabBarController {
            routeController = RouteController(root: rootVC)

        return true

    func application(_ app: UIApplication, open url: URL, options: [UIApplicationOpenURLOptionsKey : Any] = [:]) -> Bool {
        return routeController?.open(url.route) ?? false

    func application(_ application: UIApplication, continue userActivity: NSUserActivity, restorationHandler: @escaping ([Any]?) -> Void) -> Bool {
        return routeController?.open(userActivity) ?? false

    func application(_ application: UIApplication, performActionFor shortcutItem: UIApplicationShortcutItem, completionHandler: @escaping (Bool) -> Void) {
        completionHandler(routeController?.open(shortcutItem) ?? false)

In order to make URL/NSUserActivity/UIApplicationShortcutItem compatible with the RouteController, they will need to be extended to vend Route objects. A simple implementation might look like this:

extension URL {

    public var route: Route<UITabBarController>? {
        let components = URLComponents(url: self, resolvingAgainstBaseURL: false)!
        return Route.route(forIdentifier: components.path)

When dealing with URLs, in addition to vending Route objects, you will also need to configure your app with its own URL scheme. More information on this process is available from Apple.

Creating Routes

Creating a new route is as simple as creating a new Route instance.

extension Route where Root == UITabBarController {
    static var leftTab: Route {
		return Route(identifier: .leftTabRoute) { root, options -> Bool in
            root = 0

            if let routeRespondableController = root.selectedViewController as? RouteRespondable {
                routeRespondableController.setRouteAction {
                    DispatchQueue.main.asyncAfter(deadline: .now() + 2.0) {
                        print("LeftTab successfully reached!")

            return true

The above example creates a static instance of the Route struct designed to travel to the leftmost tab of the sample application. The identifier is used to differentiate this route from others when converting between types that vend routes (such as URL).

The trailing closure is the mechanism of routing. Given the instance of your root view controller, as well as any options provided with the routing request, this closure should execute the required changes to the view controller hierarchy to reach the destination. If the destination can successfully be reached, this closure should return true. Otherwise, it should return false.

Route Actions

Route Actions are closures that can be executed at particular route destinations. If the route conforms to the RouteRespondable protocol, it will have a public routeAction property which can be set inside the route. When this destination is reached, it will indicate to the routeAction an appropriate time at which to execute.


To run the example project, clone the repo, and run pod install from the Example directory first.


  • iOS 9.0+
  • Swift 5.0


Swift Package Manager

dependencies: [
    .package(url: "https://github.com/BottleRocketStudios/iOS-Scotty.git", from: "2.1.0")


Add the following to your Podfile:

pod 'Scotty'

You will also need to make sure you're opting into using frameworks:


Then run pod install with CocoaPods 0.36 or newer.


Add the following to your Cartfile:

github "BottleRocketStudios/iOS-Scotty"

Run carthage update and follow the steps as described in Carthage's README.


See the CONTRIBUTING document. Thank you, contributors!


Stars: 8


Used By

Total: 0


2.1.1 - 2019-10-07 15:12:04

Bug Fixes
  • None.

- 2019-04-30 18:54:46

Bug Fixes
  • None.

2.0.1 - 2018-09-21 15:48:25

Bug Fixes
  • None.

2.0.0 - 2018-07-18 18:46:19

  • Simplified API to allow for a single type to translate into multiple routes.

1.1.0 - 2018-05-08 19:49:21

  • Adjusted project structure to better support Travis-CI. CI is fully up-and-running on all currently supported platforms. Carthage is now required to work on the library and run the example projects (Cocoapods is no longer used). Clone the repo, run carthage update, and then open Scotty.xcworkspace to get started.
  • Some aspects of the routing interface have been simplified. The previous combination of Routable (a protocol) and AnyRoute (a type erased struct conforming to Routable) have been replaced by a single Route struct. This struct is still generic over it's RootViewController, but this change makes it easier to create new routes, while maintaining type safety. In addition, the RouteConvertible protocol was removed. This allows the same type to be converted to different Route objects, with different RootViewController, allowing more flexibility.
  • The RouteActionable protocol has been renamed to RouteRespondable. It's requirements remain unchanged.