ux-research 1 linked patterns checked
Baymard Mobile Form Usability: Avoid splitting single input entities
Reports that users often perceive names as one coherent entity, may enter their full name in a first-name field, and that splitting names can create interaction burden, required-or-optional ambiguity, and uncertainty around middle names and titles.
Read with a purpose
What this source can teach
Use this source to examine the study question, participants, observations, and limits before applying a finding.
- Start with the original. Open the source and find the guidance or example relevant to your task.
- Trace the connection. Use the claim notes below to see how this site applies the source to specific patterns.
- Check the setting. Compare the source's platform, people, and constraints with your own decision.
Pattern Decisions This Source Supports
| Pattern | Supported decision | Required contract | Claim note |
|---|---|---|---|
| Name entry | Choose name entry when the product must capture a person's name for identification, correspondence, display, official records, booking, payment, verification, support, or relationship handling. | Users can type, paste, autofill, edit, select, undo, and correct names through native text behavior. | Baymard supports avoiding unnecessary split-name fields because users often perceive their name as a single coherent entity. |
Evidence Role
This source is treated as ux-research evidence. Its value comes from the specific claims and setting described above.
Publisher: Baymard Institute. Last checked: .