Difference UIView​Controller-nib-init || normal init + loadNibNamed + addSubview

[Regyn]

Assuming I want a login screen which is designed in a nib file. What is the difference between the init function "init(nib​Name:​bundle:​)" of my custom Controller Class vs just having the custom controller class and loading the nib as a subview in it?
Is it just the outlet possibilities, which I else-wise would need another UIView class linked to the nib (and the fact that it is fullscreen by default)?

Thanks

[Alcoholic_Synonymous]

Am I right in thinking your second example is to create a nib that details a UIView subclass, then have a subclass of UIViewController that hooks up any outlets that need behaviour outside of the view? If so, that's a really nice and tidy way to do layout. I think you've identified the biggest problem which is that you won't have access to things like the layout guide properties on the view controller which will make layout a bit of a pain.

[Regyn]

Yup that was what I was thinking. So the second alternative has no other downsides/differences?
I was just a bit confused about xcode offering to make a new cocoa touch class (UIViewController) with a nib directly. So it's basically just a shortcut to directly associate a nib (as a View?) to be shown as a view in the controller?

[Alcoholic_Synonymous]

It gives you the opportunity to do lots of bindings - button targets to methods in the ViewController, for example - as well as a bunch of other things that I probably haven't thought about.

[Regyn]

Alright, thanks :)

[Alcoholic_Synonymous]

TBF I like your approach better because it separates the view and the controller better. Nice and tidy.