Design pattern for Universe app and view controllers

[nibeck]

We are in the early planning stages of a Universal app that will use navigation style interface on the phone/pod, but use the new SplitView controller on the iPad.

Apples sample generates two AppDelegates, and sets up separate and shared code and resource folders. Some examples I have seen on-line, have a single app delegate, and then instantiate appropriate view controllers based on what device it is running on.

Any recommendations on the "right" approach?

_mike

[Withered]

Originally Posted by nibeck

We are in the early planning stages of a Universal app that will use navigation style interface on the phone/pod, but use the new SplitView controller on the iPad.

Apples sample generates two AppDelegates, and sets up separate and shared code and resource folders. Some examples I have seen on-line, have a single app delegate, and then instantiate appropriate view controllers based on what device it is running on.

Any recommendations on the "right" approach?

_mike

I don't know about the "right" approach, but I designed the iPhone app, then upgraded the project to a universal app. As I designed the iPad experience, some views could remain the same (with auto resizing), others required significant changes. The more significant changes were accomplished by either creating a new view/view controller, or by deriving from the iPhone implementation and overloading/adding functionality. It seems to work fine.