A useful prelaunch audit finds assumptions that make an app fragile when its available space changes. It produces reproducible findings and a test plan. It cannot substitute for physical-device verification.
Apple’s WWDC26 session Modernize your UIKit app identifies scene lifecycle, main-screen references, device-idiom checks, and orientation assumptions as modernization areas. The checklist below translates that guidance into an independent review process.
1. Choose one important journey
Pick a task with a clear outcome: create a document, complete a purchase, review a calendar, or edit a clip. Record the app version, build, test environment, starting data, and expected result. A precise five-screen review is more useful than an undocumented claim that the whole app is ready.
2. Find fixed-layout assumptions
Review hardcoded widths, heights, screen bounds, and orientation branches. Check that layout follows the current view or scene dimensions. Watch for content that clips, buttons pushed offscreen, and sidebars that consume too much room. Test intermediate widths as well as extremes. Apple’s modernization session explains the underlying adaptation approach.
3. Preserve the user’s place
Change the available size while editing. Check whether drafts, selections, navigation, media position, and scroll position survive. Repeat with the keyboard visible and after backgrounding the app. Label any behavior you cannot exercise in an available environment as unverified.
4. Keep controls accessible
Increase text size and inspect control labels and reading order. Look for inaccessible clipped text, ambiguous controls, and actions that depend only on a visual cue. A larger display is an opportunity to improve comprehension; extra space alone does not make the workflow accessible.
5. Separate current checks from future device tests
Apple’s Duo announcement describes Device Hub support as upcoming. Use available supported simulators and previews for general adaptability work, and name that environment accurately. Reserve real folding transitions, camera behavior, thermal performance, battery, Pencil behavior, and accessory fit for appropriate device testing. Source: Apple launch release.
6. Turn findings into acceptance criteria
Write each issue as a repeatable observation: “At this width, after these steps, the primary action is hidden.” Include severity, evidence, the desired behavior, and a retest procedure. Keep speculative improvements separate from observed defects.
Example criterion: An unsent message and cursor position remain intact when the available content width changes during editing. Record the app build, environment, and observed result before marking it passed.
Request a fixed-scope readiness audit →
Sources
- Apple Developer, Modernize your UIKit app, WWDC26.
- Apple Developer, What’s new in SwiftUI, WWDC26.
- Apple, Apple unveils iPhone Duo, September 9, 2026.