ipad-layout-audit

You can detect hardcoded iPhone widths causing iPad layout regressions by scanning your iOS project for fixed frame constraints that break on iPad viewports. The audit flags hardcoded frame widths to prevent layout failures before submission.

Your app may fail guidelines 2.1 and 2.4.1 due to missing iPad orientation keys in Info.plist or absent horizontalSizeClass adaptations. The audit checks for missing UISupportedInterfaceOrientations~ipad entries and size-class adaptations to satisfy review requirements.

Check for missing UISupportedInterfaceOrientations~ipad by auditing your Info.plist for absent iPad orientation keys. The skill identifies missing iPad-specific orientation configurations to prevent review failures.

Yes, you can audit size-class adaptation in both UIKit and SwiftUI projects. The skill verifies the presence of traitCollections and adaptive constraints to ensure proper horizontalSizeClass handling across universal apps and iPad-targeted builds.

The best way to catch iPad layout issues before submission is running an iPad layout audit that checks for hardcoded iPhone widths, missing Info.plist orientation keys, and absent size-class adaptations to satisfy App Store guidelines 2.1 and 2.4.1.

The iPad layout audit works for both universal apps and iPad-targeted builds. It applies to iOS projects using UIKit or SwiftUI to identify hardcoded iPhone widths and missing size-class adaptations across any iPad-compatible configuration.