Home/ Questions/Q 7966059
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-06-04T06:19:14+00:00

I have a tricky question. As everyone knows, Apple clearly says that ONE UIViewController

  • 0

I have a tricky question. As everyone knows, Apple clearly says that ONE UIViewController should be onscreen at a given time.

But how about if you wanna implement a signup worflow, with tiny views, of say… 200px height?.

Is it there any real problem you could face.. if you attach an UINavigationController (320x200px) as a subview, and push several UIViewControllers?.

If i go the UIView approach, i’ll need to replicate the UINavigationController’s behavior. It’s not big deal, but it takes extra time.

Furthermore, UIView’s shouldn’t have business logic code. So, the rootViewController would be handling the whole signup flow. Which is OK, but i’d really rather split it up into several classes.

Any suggestions will be very welcome.
Thanks in advance!

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    You should look into the new container ViewControllers. From Apple’s Docs:

    Implementing a Container View Controller

    In iOS 5.0 and later, custom UIViewController subclasses can also act as container view controllers. A container view controller manages the presentation of content of other view controllers it owns, also known as its child view controllers. A child’s view can be presented as-is or in conjunction with views owned by the container view controller.

    See also https://developer.apple.com/videos/wwdc/2011/?id=102

    • 0