Separate nibs/xibs
In case you are wondering why you should separate your nibs/xibs in your project you are in the right post. The Apple resource programming guide explains everything in detail but we are after the following paragraph:
“In the main nib file for a Mac OS X application, consider storing only the application menu bar and an optional application delegate object in the nib file. Avoid including any windows or user-interface elements that will not be used until after the application has launched. Instead, place those resources in separate nib files and load them as needed after launch.” (link)
Having everything in one nib is in general a bad idea. The reason is that you are instantiating everything at once when the application is launching. Of-course in a tiny application you wont even notice a difference in the performance neither in the way you organise the project but when the project is expected to be big you are encouraged to separate it.
For example if you have everything in one nib/xib file you are instantiating the preferences window, about window and other windows and controllers that you may not using.
You should be using multiple nibs.

1 Comment
Really decent post… I love it. Keep ‘em coming…