Maybe you are structuring you application the wrong way, this is why you are having such problems. My team manages a large app, this is how we do (and other co

Maybe you are structuring you application the wrong way, this is why you are having such problems. My team manages a large app, this is how we do (and other companies we worked with too): Every nib has only one responsible programmer (or pair) the storyboards uses many external nibs[1]. Storyboards are not meant to act as regular nibs, xcode will get insanely slow if you have a lot of screens. They will help you build prototypes faster, documentation and navigation flow but keep in mind that mildly complex projects will force you to have a bunch of bloated prepareForSegues around, which makes them useless. [1] http://stackoverflow.com/questions/9251202/how-do-i-create-a-custom-ios-view-class-and-instantiate-multiple-copies-of-it-i/9251254#9251254 http://stackoverflow.com/questions/9251202/how-do-i-create-a...