ux-research 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.
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. Use it to validate the decision rules above, not as a visual style reference.
Publisher: Baymard Institute. Last checked: .