4 ms·
If you really need someone's full name for them to use the service, it's probably best to put it directly on the sign-up process. If not, make it optional to ad
by philh 18y ago
If you really need someone's full name for them to use the service, it's probably best to put it directly on the sign-up process. If not, make it optional to add after registering.
You may want to dispose of usernames entirely, and use their email as a unique identifier. That ought to be easier for people who aren't used to the concept of usernames.
- glen 18y agoThanks. Yes, we will need their full name. We did talk about using their email as a unique identifier, but we need to have something for their URL - like: www.nixty.com/philh
- falsestprophet 18y agoThat was my thought as well for the last application I built, but no one is going to care to find their data by url. Just use a random key to form the url: okay.com/lekaro.
- Jax 18y agoHi philh! Bug report of your thought: The second option you mentioned - about disposing off usernames and using email addresses as unique identifiers - is not feasible in glen's case, because he intends to use the unique identifer as a part of the url. @glen: collect the first name and last name only if u need them. If you just want to address your users then, you can just do "Hi [username], what's up? Bla... Bla... [some-username] has sent you a message..."