Return key label is contextually appropriate
Why it matters
The generic return key on a password field gives no signal that pressing it will submit the form — users tap the submit button anyway, making the return key dead weight. On a search field, the wrong label leaves users guessing whether return submits or inserts a newline. Contextual return keys (done, go, search, send) are a zero-cost signal that matches the platform convention and reduces form completion time.
Severity rationale
Low because the wrong return key slows users but does not block form completion.
Remediation
Set returnKeyType per field and wire onSubmitEditing so pressing the key actually advances or submits. Use refs to chain focus between fields in multi-input forms:
<TextInput placeholder="First" returnKeyType="next" onSubmitEditing={() => lastRef.current?.focus()} />
<TextInput ref={lastRef} placeholder="Last" returnKeyType="done" onSubmitEditing={submit} />
<TextInput placeholder="Search" returnKeyType="search" onSubmitEditing={search} />
DetectionPro
The detection method for this pattern is part of AuditBuffet Pro.
The full method (what to look for, pass and fail conditions, and how results get reported) ships inside the Mobile UX Patterns Audit. The pattern definition, severity rationale, and remediation remain openly licensed under CC-BY-4.0.
Taxons
History
- 2026-04-18·v1.0.0·Initial import from mobile-ux-patterns·automated