Lol ok perhaps I phrased it wrong. I'm really looking for some pros and cons. I suppose I'd be correct in thinking;
pro) quicker fleshing out simple views,
con) would still have to flesh out some of the dynamic frame work in code, plus a lot of IBOutlets..
It's not that I want to use storyboards, just wondering if i'm missing something. Early on in my app dev life I worked with someone who talked me out of using IB.. Just wondered what, if anything, I was missing out on.
Talked you out of IB.. hmm, mostly it's people who didn't really work with IB, or had something strange (that was their own fault), who talk you out of XIBs.
For easy stuff it's just trillion times faster using IB. drag image on, put the name of image in, even with autocomplete (hate that codewise Xcode doesn't has this).
Dragging buttons on there, connecting with IB.. just so easy, I can promise you, the story that Art told, I can understand that 100%, i've had it so many times, for basic mockups, it takes like 10 mins max. Just self.navigationController pushcontroller, new view you created in IB. then hook up an IBAction with same code to a new controller you created in IB, and so on. it's just so easy.
I admit I use it in all projects, because taking over a project that doesn't have it takes so much longer, because you have to perfect all the pixels by hand, rerun it, tweak it, run it again.. in IB it's like, tap arrow on keyboard 2ce, and you can see it live changing 2 pixels.
@Art, yeah, the Android is a hell.. it's faster to run it on your device then in the emulator
But again, about the storyboards, I have no idea, i started once, but gave up quickly because I don't have alot of time, and just went back to XIB's, they do everything I need and I can use them to their full extend. So no need for me to move