4 ms·
It's a good one, but it seems that there's a trade off with this design. Either you have to ask your users to enter all this information (not a good user experi
by bsvalley 9y ago
It's a good one, but it seems that there's a trade off with this design. Either you have to ask your users to enter all this information (not a good user experience), or, you end up with inconsistency in your model when you try to query by # number or email or any other "optional" Id's. Querying by UUID makes your app use cases fairly narrowed.
- ivan_gammel 9y agoNo, there's no trade-offs. From UX perspective, of course, user is not required to enter all this data. This is for his convenience, so he is required to provide bare minimum of information by his choice. However, for some functions security requirements are elevated, so he may be required to enter additional details or provide additional means for authentication.