The reason you separate different sections into multiple XIB files is twofold.
The reason you separate different sections into multiple XIB files is twofold: If the user doesn't go to each section of your app (they only select the first submenu, for example), only the needed XIB files have to loaded, reducing the memory footprint of your application. This generally isn't too much of an issue, unless you have a lot of things in your XIB, but it's always better to use memory sparingly because you don't know the users situation. When everything is split up into different files, you can potentially organize it better.
This part is completely up to you, and whether you like to have everything in one place, or broken up into categories. Basically, it doesn't matter too much for most applications which direction you go. Do whatever works for you.It is generally recommended to split the views used by view controllers out into different files (Xcode does this automatically a lot of the time).
The view controllers do the lazy-loading of the additional XIB files for you (you just have to set the NIB Name of the view controller), so it doesn't take much effort at all.
I will have about 70 views. Is that considered a lot? – Mark Worsnop May 11 at 3:53.
I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.