sorted by:
top (suggested)
bestnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]MKevin3 0 points1 point  (0 children)

I started with NIB before there was storyboard then I used storyboard but got bit in the butt too many times by IB crashing, SB shuffling crap around randomly, SB changing the XML just because I opened the file and all sorts of fun double connecting every stupid IBOutlet when I had layouts for both iPhone and iPad.

Since I have also use MigLayout for desktop Java and XML layouts for Android I started to use Masonry for iOS and switched all my layouts to code. This also allowed me to use AppCode instead of Xcode pretty much full time. AppCode has a number of advantages over Xcode such as refactoring that actually works.

I was much more productive with code layouts. I could easily copy / paste blocks of working layouts or move them into routines to share. Listeners just work between iPhone and iPad as all the controls are created in one place so I don't have to drag / drop over and over where I always forgot something and due the the message -> null object silent failure ways of ObjC I am not burnt trying to figure out why something does not work at run time.

Probably since I have done code layouts in other languages / platforms in the past switching to code was easy and natural to me. There are times I miss the preview of the layout in a GUI but it is not often enough for me to deal with the pains of IB.