Let the programming do the grunt work, not the user.ДЄ single input field is always easiest for the user - whether it's for a phone number, first and last name, social security number, or any other value that you may think of as being divided into 'parts'.

But you should be able to strip out all the unnecessary characters and spaces programatically and store it as a single field. Heck, some people will want to use a single field and type +44 (020) 444 4444 in there themselves. Then just give the user a single field and let them type in a number however they like. For instance if you know the country the person is from then you will know the format of the phone number, and if you know it's a mobile phone and not a landline then that's another clue for you to use. You should try to set up some kind of intelligence in the logic itself.

Just like with credit card numbers - we are mostly no longer expected to type 1111- 1111- 1111- 1111 in 4 separate fields and pick visa from a dropdown because there is already enough information in the credit card string itself to know the type of card, and we can easily split a single number 1111111111111111 into 4 'chunks' if that's how we need it in the back end. That's like saying 'we aren't capable of parsing a phonenumber into a format that we want, so we're going to ask you to type in it the format we want'. Which is an implementation problem and you're forcing the lack of technical nous onto the end user. The only reason for forcing a fixed format is because your back-end can't determine the format it needs. When a person dials an actual phone number with their phone, do they type 1-555-555-555 or do they type 15555555555?

Regex for number input fields html