How best to implement a separate design for the iPad in a universal app?

The essence of the question: is the app written in swift, without using the storyboard, the interface software is written using SnapKit. The interface was originally developed for the iPhone, but it's good stretched on the iPad. Now it was decided to make a completely separate interface for the iPad which now will not be able to be universal. The actual question of how best to implement this idea? To write within one project, completely new version for the iPad and software to choose how to work? I would also like to try to use Storyboard but I'm not sure this is logical because the existing interface is implemented without it.
UPD. Divided into 2 different application is not an option
July 9th 19 at 10:58
3 answers
July 9th 19 at 11:01
Have ornul to golosina with first response.
Forget the xib, this is nonsense, the storyboard can be divided into small using storyboard reference, very convenient and beautiful, so you can mark up different storyboards, one for iPad and another for iPhone, then you can ask the controllers of different classes and so on, this is set in the settings "General" in the project. Good luck)
July 9th 19 at 11:03
Not to do with rubbish and doing the layout in xib'Ah. Accordingly MyViewController.iPhone xib and MyViewController~ipad.the xib for the iPad. The system will pull the right ksib.
The problem is that the same screen on the iPad will have much more functionality than the iPhone. Additional fields appear, the buttons... Not easier in this case, you now start to cut all Storyboard—č using Storyboard reference, and then pull up on the Storyboard and the design of the iPhone? - paul.Au commented on July 9th 19 at 11:06
: storyboards lose xibom in the reuse controllers and visek. In addition to merit storyboards from a big headache. Regarding the redesign, it's hard to say without seeing the project. Sometimes a lot is at stake the proper separation of view and model-view, and sometimes a division controller for a few and then use them to parent. - Ramona_Bednar64 commented on July 9th 19 at 11:09
July 9th 19 at 11:05
Many companies use two different applications, you can also use autolayout or make two function in controller type updateIpadUI and updateIphoneUI. If you use different schemes for constructing the application, it is better to make a separate application, and if there will be all the same items but with different design, in my opinion acceptable second option. And to promote easier and to do the hot-fixes and bug fixes and the introduction of new Fitch. My IMHO do not use storyboards at all.

Find more questions by tags SwiftiOS