Choose whatever works for you. Interface Builder can save you so much time building some of the smaller aspects of your app (help&#x2F;about screens) etc. that it&#x27;s foolish in my opinion to just &quot;do away&quot; with IB on principle.<p>Sure, if you have 1 storyboard for your entire app, and 9 people are working on it, you will have collisions. 9 people on an iOS project is bound to have merge conflicts in code too, unless it&#x27;s coordinated.<p>Xcode 7&#x27;s storyboard references should help avoid some conflicts here, as it breaks up a single, conflict-magnet file into several. Hell, you can organize them like XIB files before Apple started pushing the 1 storyboard &quot;simple&quot; approach to ease the learning curve.<p>Side note: The title of this post should have been &quot;Reasons we are switching away from Interface Builder&quot;, as it doesn&#x27;t actually answer the question. But then it wouldn&#x27;t be interesting enough to click on.