Manual coding vs. Interface Builder - iPhone

Question

I have most of an app done with IB and I've managed to get things to work mostly, but I did have a lot of problems with UIDatePicker and could only get it to work properly when creating it manually.
I have some other strange bugs, like the Delete button sometimes animating accross the top of the window rather than on the row it's supposed to and based on my experience with the date picker, I don't know if that's a problem with my code or with using IB.
Also, most of the sample code seems to create things manually.
So, am I better off using Interface Builder for my iPhone apps, or creating everything manually in code? At this point I'm leaning towards doing everything manually.

Answer 1

A lot of the sample code creates elements programmatically because Interface Builder didn't exist early in the beta. Others (like UICatalog) do it to make the view heirarchy more obvious.
I usually recommend using Interface Builder wherever possible. Remember, there's nothing stopping you from altering IB-created views in your viewDidLoad method; just add outlets for the views you need to customize and connect them as needed. In my experience, it's usually easier to move parts of an application away from IB when you need to do so than it is to move them to IB to make them easier to maintain; working with pure code encourages certain design patterns (like not-really-needed view subclasses and custom constructors to avoid repetitive initialization code) that don't really play well with IB.