Agree with your question that this is difficult to solve. I would summarize the alternatives, since many of the views corresponded to the registration steps inside a single vc or vc container representing a plurality of vcs, where each of them performs the reg step.
Another alternative to the first sort (1 vc, many views) is to put many views in a large uiscrollview with paging enabled.
I don't think there is a tough and quick answer, but my pref for reg interaction is the only vc. The user probably understands reg as one step with substeps, and not as separate parts of your application (which implies switching to vc push, imo).
You are right, but IB makes the design inconvenient for this. I coped with this task in two ways: 1) just handle it, including reordering the views in ib so you can work at the very top 2) build tips for each view. load them all in viewDidLoad for a single vc. frame them in code
I recommend idea two for something non-trivial for these views. Good luck.
source share