Swift version: 5.2
Storyboards were introduced way back in iOS 5 as a way to revamp interface design for iOS. At the time they didn't add much in the way of features that weren't available with the older XIBs, but in subsequent releases Apple have added helpful new features such as layout guides that make them much more useful – and arguably indispensable since iOS 7.
All new iOS projects come with at least one storyboard ready to use: Main.storyboard. Inside that you can create as many interfaces as you want, each representing one view controller in your app. You can then design in segues (pronounced "segway", like the gyro-bike things) that transition between view controllers – all without a single line of code.
There is one drawback to storyboards, and it's something you'll hit fairly quickly: if you have more than four view controllers in your app, you'll probably find it a little cumbersome to navigate around, particularly if you're working on a laptop. If you're working on something important, move your view controllers around: keep them organized from the beginning, otherwise your storyboard will soon become a nightmare!
SPONSORED Would you describe yourself as knowledgeable, but struggling when you have to come up with your own code? Fernando Olivares has a new book containing iOS rules you can immediately apply to your coding habits to see dramatic improvements, while also teaching applied programming fundamentals seen in refactored code from published apps.
Available from iOS 7.0 – see Hacking with Swift tutorial 1
This is part of the Swift Knowledge Base, a free, searchable collection of solutions for common iOS questions.
Link copied to your pasteboard.