This document discusses the benefits of building iOS apps without Interface Builder including avoiding context shifts, inheritance issues, and performance problems when using constraints and storyboards. It provides code examples for initializing a window and navigation controller programmatically in AppDelegate, loading views directly in code instead of a storyboard, and demo apps using common UI elements like login screens and table views without Interface Builder.

1. How To Build iOS Apps Without
Interface Builder

2. But why?

3. IB vs. Code (I)
• Context shift
• More evil conflicts
• Options all over the place
• Harder to get help
• No betas for you

4. IB vs. Code (II)
• No inheritance
• Harder to DRY
• Hard to see contraints
• Really bad performance

5. Delete Storyboard

6. AppDelegate.swift
import UIKit
@UIApplicationMain
class AppDelegate: UIResponder, UIApplicationDelegate {
var window: UIWindow? = UIWindow(frame: UIScreen.mainScreen().bounds)
func application(application: UIApplication,
didFinishLaunchingWithOptions launchOptions: [NSObject: AnyObject]?) -> Bool {
window?.rootViewController = ViewController()
window?.makeKeyAndVisible()
return true
}
}

7. UINavigationController
import UIKit
@UIApplicationMain
class AppDelegate: UIResponder, UIApplicationDelegate {
var window: UIWindow? = UIWindow(frame: UIScreen.mainScreen().bounds)
func application(application: UIApplication,
didFinishLaunchingWithOptions launchOptions: [NSObject: AnyObject]?) -> Bool {
window?.rootViewController = UINavigationController(rootViewController: ViewController())
window?.makeKeyAndVisible()
return true
}
}

8. Loading The View
override func loadView() {
view = FirstView()
}

9. Demo
• Login-Screen
• Auto Layout
• UIStackView
• UITableView / UITableViewCell
• UINavigationController
• UITabBarController