如何在Size Classes下共享UIStackView内外的同一UIButton组件？

Awesome question—this is a super common pain point when adapting layouts between iPhone and iPad, and I’ve got a clean, maintainable solution that avoids duplicate buttons or IBOutlets entirely:

You only need one UIButton and a single IBOutlet (e.g., @IBOutlet weak var actionButton: UIButton!)—no duplicate components or multiple outlets required. Here's how to set it up:

Step 1: Set Up the Base Layout (iPhone-First, or Vice Versa) #

• Start by adding the button directly to your UIStackView, configure the stack view's properties (axis, spacing, alignment, etc.) to look right on iPhone sizes.
• Add any necessary internal constraints to the button (like fixed width/height, if needed) that should apply across devices.

Step 2: Configure iPad-Specific Layout with Size Classes #

• In the xib's bottom toolbar, click the Size Class selector (the wAny hAny button) and switch to wRegular hRegular (the standard Size Class for iPads).
• Remove the button from the stack view's arranged subviews: Right-click the stack view, find your button in the menu, and uncheck "Arranged". Alternatively, in the Document Outline, drag the button from the stack view's "Arranged Subviews" list up to the parent view level.
• Now position the button directly in the parent view, add iPad-specific layout constraints (e.g., pin it to the top-right corner of the parent view, or align it with another component). These constraints will automatically be scoped to the wRegular hRegular Size Class.

Step 3: Verify iPhone Layout Works as Expected #

• Switch back to the iPhone Size Classes (wCompact hAny for portrait, wCompact hCompact for landscape). Confirm the button is still in the stack view's arranged subviews, and all original stack view constraints are intact.
• If you hit constraint conflicts, check the constraint's Size Class scope: Make sure iPad-only constraints are only active for wRegular hRegular, and stack view-related constraints are active for iPhone's Size Classes.

Bonus: Optional Code Tweaks (If Needed) #

If you need device-specific logic for the button, you can use the single IBOutlet directly in code:

if UIDevice.current.userInterfaceIdiom == .pad {
    // iPad-specific button behavior
    actionButton.titleLabel?.font = UIFont.systemFont(ofSize: 18)
} else {
    // iPhone-specific button behavior
    actionButton.titleLabel?.font = UIFont.systemFont(ofSize: 16)
}

Why This Works So Well #

• No redundancy: Reuse the exact same button and IBOutlet across both device types.
• Visual configuration: All layout work is done directly in the xib, so you can see exactly how it looks on each device without digging through code.
• Native system support: Uses Apple's built-in Size Class system, which is designed for exactly this kind of adaptive layout scenario—so it's future-proof and easy to maintain.

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