iOS Swift中如何为多个ViewController复用同一StoryBoard？

Hey there! Copy-pasting Storyboards for 10+ similar screens is such a tedious, error-prone approach—you’re totally right to seek a better solution. Let’s walk through the most practical fixes tailored to iOS development:

If your screens share entire view controllers or navigation segments, extract those repeating parts into a separate Storyboard file. Then use Storyboard References in your main Storyboards to link to this shared file.

• How to do it: Create a new Storyboard, move the reusable view controller/segments into it. In your original Storyboards, drag a "Storyboard Reference" component from the library, set its "Storyboard" property to your shared file, and pick the initial view controller or a specific identifier to link to.
• Bonus: Any changes you make to the shared Storyboard will automatically reflect across all references—no more copying and pasting updates!

Wrap all common logic and UI setup into a base class, then have each of your 10 view controllers inherit from it. This keeps duplicate code out of individual screens.

• Example: Put shared navigation bar styling, button tap handlers, loading states, or even common IBOutlet connections for repeated UI elements (like a header label or back button) in a BaseReusableViewController.
• Subclasses only need to handle screen-specific details—like setting a unique title, adding custom UI elements, or overriding specific methods when needed.

For repeating UI modules (like a custom header, footer, or form input group), turn them into standalone XIB files. Then embed these XIBs into your Storyboard screens.

• How to embed: Drag a "View" component onto your Storyboard scene, set its custom class to the one linked with your XIB, and in the "Identity Inspector", fill in the "XIB Name" field with your XIB's filename. The view will automatically load the XIB's layout.
• This way, you only maintain one copy of each reusable UI element—update the XIB once, and every screen using it gets the change.

If you want to ditch Storyboard duplication entirely, build your shared UI programmatically. Create a helper class or extension that generates the base screen structure, then let each screen tweak it as needed.

• Quick code example:

  class ScreenFactory {
      static func makeBaseScreen(withTitle title: String) -> UIViewController {
          let vc = UIViewController()
          vc.title = title
          
          // Add shared elements: navigation bar buttons, background color, footer button
          let footerButton = UIButton(type: .system)
          footerButton.setTitle("Submit", for: .normal)
          footerButton.addTarget(vc, action: #selector(vc.handleSubmit), for: .touchUpInside)
          // ... layout logic for footerButton
          
          vc.view.addSubview(footerButton)
          return vc
      }
  }
  

• Then in your specific screen:

  let profileScreen = ScreenFactory.makeBaseScreen(withTitle: "Profile")
  // Add screen-specific UI like a profile image or text fields
  

Don’t forget the design side! Put all shared colors, fonts, icons, and images into your project’s Asset Catalog. Then use these assets consistently across all Storyboards or code.

• For even more consistency, use the UIAppearance protocol to set default styles for controls (like all buttons having rounded corners or the same font) in one place, instead of configuring each control individually in Storyboards.

Final Recommendation #

If you want to keep using Storyboards, start with Storyboard References + XIBs—it’s the least disruptive change. If you’re open to more control, a base view controller class or programmatic UI will give you cleaner, more maintainable code long-term.

内容的提问来源于stack exchange，提问作者gopal