Select devices around screen space and support
Use your product support policy and audience data to choose a smaller and larger iPhone when both matter. Add an older supported configuration or the model named in a customer report. Apple layout guidance describes safe areas as part of arranging usable content. Check that your own controls and text remain reachable around system-reserved screen space.
Follow the keyboard through the form
A form can appear correct until the keyboard opens. Apple provides a keyboard layout guide because the keyboard changes the area available to an app. In your test, focus each important field, move to the next input and trigger validation. Check whether the current field, error message and submit action remain discoverable without losing previously entered data.
Name the app or browser target
An installed app requires a compatible build and agreed installation setup. A Safari test starts with a website URL and browser environment. If your product moves between an app and web pages, include the handoff, return and session state in the plan. Record which target failed so a browser issue is not filed as an unexplained app defect.
Review readable content and interruption recovery
Try the longer text states your product actually serves, such as translated labels, detailed errors and a full address. Check your supported text enlargement settings as well as orientation. Apple accessibility guidance encourages support for larger text. Also leave and return to the journey where practical, then check that the user understands whether to continue, retry or start again.
Your testing checklist
- Confirm the model, iOS version and app or browser target
- Complete onboarding and authentication with test accounts
- Review content around system-reserved screen areas
- Enter long values and recover from validation errors
- Check supported larger text and orientation states
- Record the build, steps and final outcome for each issue
A practical workflow
Choose a customer task
Define one complete journey and its expected confirmation.
Shortlist iPhone configurations
Prioritize screen sizes, OS versions and reported issues, then request coverage.
Repeat the full interaction
Test input and recovery states, capture failures and retest the same environment.
Common questions
No. Safari exercises a website in a browser. An installed app uses its own build and integration with the operating system. Keep separate targets and evidence for both.
Start with the devices your customers use and your documented support target. A new model may be relevant, but it does not replace checks on existing supported configurations.
Build format, signing and installation requirements need review. Include these details with your request, and the team will confirm a suitable setup before activation.
Technical references
Official documentation for the underlying testing concepts. Available capabilities vary by provider and setup.
Apple Human Interface Guidelines: layoutApple Developer: UIKeyboardLayoutGuideApple Human Interface Guidelines: accessibility