iPhone xcode code vs interface builder

I've been using Xcode for a while and had a brief look at the interface builder when I first started but then went straight on to coding everything.

So far it's working OK but I just wondered if I'm missing something b开发者_JS百科y not using the IB.

Is there any advantage to using the IB at all? I've even coded subviews and stuff without using the IB but I can't help thinking that it might be more advantageous to use it?

If not I'll keep on doing what I'm doing as it's working for me up to now :D

Thanks

If constructing everything in code is working for you, then great. Personally if it can be done in IB it's done in IB.

I'd be surprised if there's a best practice for this; everyone will have their opinion and preference.

I like to do UI related work in IB - if i'm dealing with presentational concerns I like to be in an environment that offers immediate visual feedback. It also cuts down the amount of boiler-plate code that you would have if constructing everything programmatically.

That said you can't do everything in IB. There are times you'll fall back on programatically constructing or laying out a view.

A little knowledge of both approaches goes a long way...

possible duplicate of: iphone app best practice - is using the IB a better way to design your app, or writing UI code on your own better?

at the end of the day its whatever you feel more comfortable doing. IB is horrible in my opinion, programming takes more effort - more thought. :)

I usually use IB, get immediate visual feedback and make the layout looks exactly easier. Only in one case that I have to give up with IB is performance with UITableView scrolling. In this case, the best solution I can find is to write code to draw everything in the cell using code. This makes the performance much better.

Generally, I recommend to use IB until you have some specific requirements like performance or you need to have really much control over the view

New projects always start off simple so people tend to gravitate toward IB naturally. Personally I've found that as a view gets more dynamic and complex (and they always do), it makes sense to code it.

YMMV.