The iPhoneRant blog reflected my experience pretty well with posts like this:
http://www.iphonerant.com/2009/06/xcode-is-flaky-interface-b...
http://www.iphonerant.com/2009/06/hahahahaha-wow.html
Quotes: "Programming the iPhone means managing a hodgepodge of view and view controllers and nav controllers and where the hell was I? It really doesn't allow your brain to just think about what the software is supposed to do. The fact that no one's come out with a good source to teach this stuff is very telling--it's unteachable. You have to slog through it, and when you get it to work, you're done. You can't necessarily explain how you got there or why it works. And it doesn't lend itself to being teachable, which is a good reason all the books on iPhone programming stink."
"The XCode environment is flaky and shit-filled. Little things add up, like the fact that you can't just select a file in the top frame and save it with command-S. No, you get a beep. Can't do that. You have to CLICK IN THE LOWER WINDOW, on the code, and then hit save. Because, otherwise you might save a few clicks and make things easy and intuitive."
I've actually got an App in the store. When I started I figured I'd do this silly little thing as a proof-of-concept and then go on to more ambitious ideas but I gave up because iPhone programming was just so unpleasant I couldn't bring myself to do it anymore.
I commented on UIBuilder here: http://blogjack.net/2009/06/why-do-iphone-development-tools-...
And on the early DRM experience here: http://blogjack.net/2008/07/iphone-20-woes.html
My hope is that one day Apple produces an Apple-worthy development environment.for iPhone OS. XCode/UIBuilder isn't it.
The same scenario has repeated itself for many years: a newbie gets annoyed at IB and says "I'm just gonna do it all in code!" and all the graybeards say "ur doin it rong."
It's obvious that your UI is easier to modify and update using IB than hacking it in and out of the view controller code.
Back to the original thread, I do give a little credit to Android to having the option of UI editing done inside of Eclipse. It's not perfect, it's a little hacky, but the concept of slapping down a UI element like a button, naming it, and then having it automatically compile and show up in the editor autocomplete is a powerful thing. The first time it happened it honestly was a nice surprise.
While this is a great feature for reasoning about your xibs, it can probably seem unnecessarily confusing to someone new to Cocoa.
For my first "hello world" apps I wound up coding the views entirely by hand and skipping the .xib