General: why use XIB's instead of a storyboard

I see that in some example templates XIB’s are used instead of a storyboard file. Are there reasons and/or advantages for using this “old” method? I’ve learned to always use storyboards.

Personally, i don’t like having the whole GUI of the app in one single file. its a pain to maintain, more prone to merge conflicts in larger teams and, in general, IMHO, cumbersome to on ion Xcode unless you have a 2000" screen.

With xibs. each view/window is self-contained and separate.

Yor not use one code file for your entire application; so why would you want to use a single (opaque weird and not human-fixable xml) file for your entire GUI? But that’s just me.

I’m with you :). Structure is king.

Problem is that they teach you storyboards everywhere, so it’s a bit hard to find documentation of the workflow to create apps with XIB’s. That’s why I’m glad you added the new template with multiple screens. Just the right info I needed.

NB: If you know of good documentation that describes working with XIB’s; let me know :wink:

1 Like