The tipping point for IB came with Auto-Layout. Realtime feedback when setting up constraints makes a huge difference. The risk of merge conflicts, can be alle

The tipping point for IB came with Auto-Layout. Realtime feedback when setting up constraints makes a huge difference. The risk of merge conflicts, can be alleviated by breaking down your massive storyboard into smaller ones that deal with each flow. If that doesn't setup appropriate boundaries for your teams, break them down into one storyboard per view controller. If that isn't modular enough, use XIBs to at least layout views. The merge conflict argument is overrated. The vast majority of apps don't need more than a few developers working on user facing code. You're building an iPhone app, not an operating system. As far as I can see the only way to easily review changes made using Interface Builder, barring getting really good a reading raw XIB files, is to manually checkout and review each pull request. Doing this is of course incredibly tedious, time consuming and not something I suspect most people have the discipline to do consistently. In Gerrit, code reviews include a one-liner you can copy and past to checkout the branch up for review. Regardless of the IB debate, if your code review tool doesn't do this, invest in tooling to make checkouts as frictionless.