Usually I wouldn’t get involved in arguments about which configurations framework designers choose to make default, but in the case of the iPhone’s UITableView, it’s pretty apparent the default options are going to lead you in circles of UI Case Study research and aesthetic ponderings before you realize a flip of a switch will solve 90% of your problems.
And I mean, come on. There’s a reason we’re not developing for Nokia. The iPhone’s beautiful by default, right? Right?
Let’s check out a boring iPhone app with the boring UITableView defaults running on a device:
Boring iPhone App
And the Boring App’s default configuration in Interface Builder:
Boring Interface Builder Default Configuration
But let’s flip the switch on that mofo and make a beautiful application with beautiful design:
Awesome Interface Builder Default Configuration
Oh, SNAP. I bet you know where I’m going with this.
Here’s our AwesomeApp in the state of being Awesome and being edited to be even more Awesome:
Awesome App Being Awesome
Awesome App Being Edited Into Even MOAR Awesomez
