Profiling registration forms that take either email OR phone number

Question

Profiling registration forms that take either email OR phone number

stuartpb opened this issue 8 years ago · 5 comments

Basically, Facebook's registration form has a double-field that can be either your email address or a phone number. Only one is required, but you do have to enter it twice (unlike the password, which you only enter once).

Maybe there should be a registration.form.contact with an accepts (and a corresponding repeat) that can act as an alternative to registration.form.email and/or registration.form.phone?

Answer 1 · 2017-02-10T12:14:39.000Z

Putting this on the "future" milestone because I'm not certain I want to undermine registration.form.email this way so soon after establishing it.

Answer 2 · 2017-02-11T22:52:37.000Z

Honestly, because this is pretty much unique to Facebook... hm. I'm thinking this might just mean registration.form has to have a notes (or caveats) that explains this.

Answer 3 · 2017-02-14T07:12:31.000Z

Twitter has the same "phone or email" input, so I think it's worth figuring out.

Answer 4 · 2017-02-14T10:22:41.000Z

Moving this to v0.1.0 because, yeah, I don't want Facebook and Twitter to ship with a major component of their registration undefined like this.

Answer 5 · 2017-02-28T22:04:05.000Z

Eh, Facebook has email listed as a required input, and Twitter's registration is weird and not-easily-deterministic (varies depending on outside factors like having had a registration originate from your IP address recently) and multi-phase anyway (and the contact aspect is described in a note), so I think I can accept having these be a little under-served until v0.2.0.