Auto Layout vs. Manual Layout for Dynamic Type Support in Custom UI Elements

The Verdict: Manual Layout for High-Density Components

For a custom component containing 30+ labels, manual layout in layoutSubviews is the superior choice for balancing performance and maintainability. While Auto Layout simplifies the initial setup, the computational cost of solving a constraint graph for dozens of interdependent elements during a Dynamic Type transition often leads to perceptible main-thread hitching.

Performance and CPU Usage

In a view with 30 labels, manual layout yields lower CPU usage during Dynamic Type changes. Auto Layout relies on the Cassowary linear constraint solver; every time a font size changes, the engine must re-evaluate the entire relationship graph to determine new frames. Manual layout replaces this solver with simple arithmetic (addition and subtraction of frame origins and sizes), which is orders of magnitude faster for large numbers of subviews.

Implementation Guide for Manual Layout

To implement Dynamic Type support manually without drift or layout errors, follow these steps:

1. Enable Automatic Updates: Set adjustsFontForContentSizeCategory = true on all labels. This ensures the font updates automatically without requiring a manual font assignment on every notification.
2. Trigger Layout Passes: Override traitCollectionDidChange(_:) (or use the UIContentSizeCategoryDidChange notification) to call setNeedsLayout(). This forces the system to invoke layoutSubviews.
3. Calculate Frames Dynamically: Inside layoutSubviews, use sizeThatFits(_:) or intrinsicContentSize of the labels to calculate the required height and width based on the current font metrics.
4. Avoid Hardcoded Constants: Use relative offsets and system-provided spacing constants rather than fixed pixel values to prevent clipping at extreme accessibility sizes.

Accessibility and VoiceOver Integration

Updating accessibilityElements: VoiceOver relies on the frame of the view to determine the focus rectangle. Because manual layout updates the frame property of subviews during layoutSubviews, VoiceOver automatically reflects the new geometry. No manual update to the accessibilityElements array is required unless you are changing the order of elements or grouping them into new containers.

AccessibilityTraits Guarantees: Auto Layout provides no specific guarantees regarding accessibilityTraits during font changes. Traits (such as .button or .header) are properties of the view object and are independent of the layout engine. Whether you use manual or automatic layout, traits persist across size changes.

Assumptions and Verification

This recommendation assumes the use of UIKit (iOS 13+). To verify the performance gain, use the Instruments Time Profiler during a Dynamic Type change to compare the time spent in UIViewLayoutConstraint versus layoutSubviews. Use the Accessibility Inspector in Xcode to ensure no text is clipped at the 'Accessibility Extra Extra Extra Large' setting.

Diagnostic Detail Needed: Are these 30 labels arranged in a simple linear list or a complex nested grid? A linear list further reinforces the choice of manual layout, whereas a highly nested grid might necessitate UIStackView (which uses Auto Layout internally).