Inputs are single-line fields for a typed value: a header that names the field, a shell with room at either end for a mark or an action, and a footer that reports what the value earned. The eight blocks here are one shell doing eight jobs, among them a search that narrows a list as you type, a masked password with its rules underneath, a phone number split from its dialling code, a card number, a URL with a chosen scheme, and a read-only link with a copy control.
The shape of the value decides the field, and that shape is rarely typed. Card digits regroup once the number names its issuer, 4-4-4-4 for most and 4-6-5 for Amex, and a phone number regroups when the country changes, so part of each of those fields is a chooser rather than a keyboard. Error state then belongs only to the segment that can be wrong: a dialling code is never invalid, and tinting it because the number beside it is points at the wrong thing.
A payment form where the number regroups as the issuer becomes clear and a provider mark appears at the trailing edge, so the person can see the number was understood before they submit anything.
A registration form taking a phone number from anywhere. The dialling code is a segment the person picks, the digits regroup to the country chosen, and Verify sits inside the box holding the number.
A field above a list of people that filters as characters are typed, with a clear control once there is something to clear and a filter box at the trailing edge for narrowing by attribute.
A generated URL shown read-only on a muted surface with a copy control welded to its edge, and the expiry stated in the footer so nobody sends out a link that is already dead.
No. Placeholder text disappears the moment someone starts typing, which removes the only description of the field exactly when it is being filled in, and it leaves nothing to check against when a completed form is reviewed before submission. Keep a persistent label above the field, and use the placeholder for an example of the expected format if you use it at all.
Validate first when the field loses focus, so a half-typed email is not marked wrong while it is still being typed. Once a field has already shown an error, switch to validating on each keystroke so the error clears the moment it is fixed rather than at the next blur. Password rules are the exception: they are a checklist being satisfied, so they update live.
Join the Orvain Dispatch and get production-ready components, free to keep: React and Vue code plus the Figma frame, yours to ship.
Inputs are single-line fields for a typed value: a header that names the field, a shell with room at either end for a mark or an action, and a footer that reports what the value earned. The eight blocks here are one shell doing eight jobs, among them a search that narrows a list as you type, a masked password with its rules underneath, a phone number split from its dialling code, a card number, a URL with a chosen scheme, and a read-only link with a copy control.
The shape of the value decides the field, and that shape is rarely typed. Card digits regroup once the number names its issuer, 4-4-4-4 for most and 4-6-5 for Amex, and a phone number regroups when the country changes, so part of each of those fields is a chooser rather than a keyboard. Error state then belongs only to the segment that can be wrong: a dialling code is never invalid, and tinting it because the number beside it is points at the wrong thing.
A payment form where the number regroups as the issuer becomes clear and a provider mark appears at the trailing edge, so the person can see the number was understood before they submit anything.
A registration form taking a phone number from anywhere. The dialling code is a segment the person picks, the digits regroup to the country chosen, and Verify sits inside the box holding the number.
A field above a list of people that filters as characters are typed, with a clear control once there is something to clear and a filter box at the trailing edge for narrowing by attribute.
A generated URL shown read-only on a muted surface with a copy control welded to its edge, and the expiry stated in the footer so nobody sends out a link that is already dead.
No. Placeholder text disappears the moment someone starts typing, which removes the only description of the field exactly when it is being filled in, and it leaves nothing to check against when a completed form is reviewed before submission. Keep a persistent label above the field, and use the placeholder for an example of the expected format if you use it at all.
Validate first when the field loses focus, so a half-typed email is not marked wrong while it is still being typed. Once a field has already shown an error, switch to validating on each keystroke so the error clears the moment it is fixed rather than at the next blur. Password rules are the exception: they are a checklist being satisfied, so they update live.
Join the Orvain Dispatch and get production-ready components, free to keep: React and Vue code plus the Figma frame, yours to ship.
They get an email with a link that expires in 7 days.
Paste or type addresses. A comma, a space or Enter adds each one.
They get an email with a link that expires in 7 days.
They get an email with a link that expires in 7 days.
Paste or type addresses. A comma, a space or Enter adds each one.
They get an email with a link that expires in 7 days.