TTNavigator on IPad

Question

I want to start using THree20's TTNavigator in my app, however I read here that it shouldn't be used on IPad.

I don't really get the explanation, and what using url browsing mechanism has to do the with the IPad screen size.

Did anyone encountered problem with TTNavigator on IPad ?

I don't want to start using to later find out I have problems running the app on an IPad.

Answer 1

The reason is that TTNavigator is written so that it adds a TTNavigationController to the application's window. You can use it in this fashion if you'd like and it will work but that's not how most developers want to use it on the iPad. We want to be able to have a a TTNavigator control the view hierarchy in one (if not both) of the view controller(s) in a split view.

Because TTNavigator is designed to work automatically on the app's key UIWindow it doesn't directly support being added as a view controller in a UISplitViewController.

You can hack Three20 to make it work or you can wait a few more weeks for official support from the Three20 developers.

Answer 2

The iPad has a larger screen to accommodate more than one view at a time, as an example, look at UISplitViewController.

The point being made is that TTNavigator expects to control the whole screen, meaning only one view will be visible at a time, which almost (but not entirely) goes against the philosophy of the iPad.

iPad users expect to be able to see and do more on an iPad than they would on an iPhone because of the larger screen size. Larger size means more space for multiple touches, more space for extra content and information and interactivity.

There's no technical reason why you shouldn't use TTNavigator on an iPad - only usability / user experience reasons.