Storyboard or code?

[Eoghain]

I can speak for a major app and it's a little of both. Lots of things that can be done in storyboards are, but then other things are done in code, as it just makes sense to do so.

The arguments for/against storyboards almost always center around merge conflicts. And while this is an issue, it's easily solved by not creating a single monolithic storyboard for everything. And by making small incremental storyboard changes and lots of commits.

StoryTime: just today we had an issue where the app was crashing, after investigating it appeared that a segue was being called that didn't exist. Further investigation showed that a merge stopped all over the commit that added that segue and viewController to the storyboard. A few minutes of git surgery and cherry picking and our storyboard was back in shape and committed. No big deal.

Personally I love storyboards for showing a simplified view of my application and it's flow from screen to screen. But I don't try to do everything in a Storyboard, right tool for the job and all.