THE ADAPTATION CHECKLIST
Adaptation checklist
Review layout, state and delivery. Keep a record of what you verify.
Saved only in this browser’s local storage, not sent to a server. Clearing browser data removes your progress.
01Scope & environment
Record this build and test environment
Record the host OS, full Xcode version, SDK, app build, simulator target, or device OS.
Related guide ↗Define compatibility, correct adaptation, and experience-improvement scope
Identify the most important user task and explicit exclusions for this round.
Related guide ↗Keep an original build for comparison
Record baseline behavior and known issues so they are not mistaken for new regressions.
Related guide ↗02Design & layout
Check content priority in compact and roomy spaces
Essential content remains reachable; column changes do not interrupt the primary task.
Related guide ↗Check safe areas and custom navigation
Observe multiple contexts; do not assume equal insets on opposite edges.
Related guide ↗Check important controls around folding-related regions
Verify on the actual target, not against a web illustration.
Related guide ↗Check long copy and empty states
Include multiline headings, errors, empty lists, and overflow.
Related guide ↗03State & interaction
Preserve form drafts through layout changes
Resize while typing and record field values and validation state before and after.
Related guide ↗Keep selection and navigation context sensible
After the detail layout changes, back navigation and list selection match the design.
Related guide ↗Prevent unintended duplicate requests from layout callbacks
Verify using network or business logs, not the interface alone.
Related guide ↗Keep dialogs and overlays operable and dismissible
Change layout while they are open; check occlusion, close controls, and focus.
Related guide ↗Define restoration behavior for unfinished work
Record drafts, media, and operations following scene or background restoration.
Related guide ↗04WebView & input
Agree native / web ownership of available space
Identify who handles safe areas, scrolling, and keyboard occupation; avoid double compensation.
Related guide ↗Do not unintentionally reload web content on resize
Record components, routes, page instances, and network activity.
Related guide ↗Keep inputs and submission controls reachable with a keyboard
Include focus changes, long forms, and errors; do not rely solely on dvh.
Related guide ↗Check long-list scrolling and positioning
Narrowing and restoring space follows the intended scroll behavior.
Related guide ↗05Testing & delivery
Verify larger text and assistive interactions
Record text-size and accessibility settings, not only standard screenshots.
Related guide ↗Verify third-party SDKs separately
Cover the camera, map, payment, or media components the app actually uses.
Related guide ↗Record simulator and real-device outcomes separately
Name outstanding device checks; do not substitute one evidence category for another.
Related guide ↗Assign owners to issue retests and release checks
Unresolved issues do not pass. Recheck submission requirements before release.
Related guide ↗Not applicable and Issue count as reviewed, but not as passed. Add your environment, evidence, and reasons for exclusions to the exported record.