Ah that’s going to be tricky – is moving away from Material Design’s form fields out of the question?
I say this because on top of the problem you raise, float labels have a load of usability issues.
If you’re particularly interested in designing forms that are easy to use, check out Form Design Patterns published by Smashing Magazine.
I cover all these ...
Users will appreciate if it is simple for them and it's helpful if you can capture the name in one field - seems the name format is not that important. This opens up for an even more user friendly option.
By exploring options visually it might become clear what the simplest option is. I'd say "just ask for name and do not prescribe a format".
Note: This answer is based on the fact you don't have any user feedback at this time.
Go with the drop down filter, not the tabs.
As you have rightly said, the benefit of the tabs approach is easier for the user in that it turns a 2-click process, into a 1-click process.
However, this is only really going to be beneficial if the user is expected to change ...
Good question to go with.
Also I am sure you have a good assumption and empathy towards the design decisions too.
I agree to your statement on it takes 1 interaction more to filter from dropdowns.
The second image is similar to a Chip that is designed and defined in Material Design System.
Do take a look at ...
I‘d go with option 2 (validate the field if it has been filled out)
Option 1 (no validation) – users may provide an invalid phone number and means you cannot contact them as they expected.
Option 3 (warn the user it might be wrong but let them continue anyway) – this is interesting but a bit of a copout in that you think there's a problem with the phone ...
I think it depends on the actual design of the entire input form rather than looking at this field separately, but without any screenshots this would be my best guess at which strategy applies best in which situation.
If this is an input that is expected to receive a reasonable amount of entries (for example, you have a large enough user base or potential ...
In my experience, every field is required unless otherwise indicated. This is a HUGE ongoing debate but in my experience and testing with my users I only show input fields that are required. However, if you do want to show an optional field, add an optional indicator.
Phone Number (Optional)
Treat it like any other input field. Once it has a value, it is ...