Be warned: going universal is a bigger job than you expect it to be, regardless of how complicated you expect it to be. We did this recently with Folio+. It tur

Be warned: going universal is a bigger job than you expect it to be, regardless of how complicated you expect it to be. We did this recently with Folio+. It turned out to take us about four times as long as we were expecting to produce a port that we're still not thrilled with. The basic problem is trying to make your UI feel self-consistent and platform-consistent, as the two frequently end up playing against each other. It's probably easier to go from iPhone->iPad (we went the other way), but you can't just expect to flatten a few things out into UISplitViewControllers and have everything look great. Doing it over again, I'd have focussed on our core product for iPad for longer rather than immediately trying to go universal. It makes every feature we add from here on out a much larger QA headache, and hasn't been worth it in terms of gaining access to the much larger market of iPhone users. + Shameless plug: http://ballisticpigeon.com/folio http://ballisticpigeon.com/folio