Tag Info

New answers tagged

1

If you really want a great deal of security for your transactions, you should probably do it like banks (I heard they are very security concious ;-) So the User logs in with his username + password, then he proceeds to do his various transactions - when he wants to commit his transactions to the system, he has to verify the transaction with an ...


2

As security is a major concern in this platform, it's always best to err on the side of caution. However, you also want to be careful not to encumber the application with constant requests for authentication. Although it's arguably more secure to keep asking for proof of identity for every action, it rapidly devolves into a bad user experience. Two-factor ...


0

One form would not necessarily mean a better user experience. A better user experience can sometimes be defined as a "just right fit" for the user. If your user needs to experience certain fields and messages to experience this "just right fit", then you may need two forms after all. On your site: You could have one link on the homepage that says "Sign ...


0

Considering the context of use and the user story, there must be a quick to deploy, yet routinely and robustly secure display of data. A scene based approach would conceptually strongest UX. e.g. User selects a scene need to prove I am legal drinking age in this State need to prove level of medical cover need to prove I am in an age range need ...


0

Do a quick comparative analysis I'd start by checking how other companies handle this problem, in adjacent spaces. For example, ride-share software apps such as Uber obviously need to sign up transporters and people who want to be transported. But if you already know that you need one form, then read on.... One starting point, two paths In the profile, ...


2

To require user account before use of a new and possibly unknown application may be a bad choice. Instead of two levels of users (free and premium) you may need a third level. This should be the one where users can try the application without signing up so they know if it’s worth the effort to sign up. Experienced user already have numerous of dead accounts ...


1

To answer your question: Yes, you can! But, really, I believe this might be more than changing that green notice. Here's what I would do and why (this depends on who your target audience is and what your team is willing to build, so pick and choose as you please; any of the following will help): Login Form Remove asterisk and "denotes required entry" ...


1

I understand that you need most logged customers. However, as @ChrisF said, it's not a good practice to force registration. As pointed out in the recent NNG article, if you need the user to register, highlight the benefits of registration from the users’ perspective and not the company’s perspective when asking users to register. NNG had also done a ...


0

It's great to create an account together with the purchase. But instead of sending an automatically generated password sending a link asking the user to create a new password would be appropriate. You can also provide a link to discard the account if they don't want to have an account. If it's an automatically generated password some may use it for the very ...


3

You should only create an account when it's strictly necessary and then only if the user wants to make an account. If possible you should allow users to complete a transaction as a "guest" whereby they enter all their details but these are only stored with the current order and not used to create an account. You can suggest to the user that they create an ...


1

You can start by defining the priority of the fields: Primary fields are fields that must be mandatory otherwise the system can’t even work. For example an email needs to be verified before a user can access the application. Secondary fields are fields that you should make mandatory otherwise the application has no value for the user or for the customer. ...


1

The stack exchange has the answer for your question. you can use highlighted pop up kind of messages show up for mandatory fields like the Username, mail and CV kind of fields one by one while the user leave any field empty.


0

Some fields are more important (CV), some less (driver license), but this should not be communicated to the user. It's not about telling the user the importance to the recipient of each field, you just have to visually communicate which fields are mandatory and which are not. The convention is to use an asterisk beside a label, but you should always ...


1

Keep in mind that depending on the age of the students not all of them will have a mobile number, so you'll either need to allow a phone number (the parents) be used for more than one account or have email as a secondary option. I think the key point you're missing is that facebook lets the user choose if they prefer to use an email address or mobile number. ...


2

Mobile numbers will go away within a couple of years. Email is ageless technology. The difference is that in most countries a mobile phone number should be linked to a personal ID (passport/security ID, etc.) In mobile-oriented site or app it could be mindful to auth by phone no., but a user could have no one. Linking to the mobile number, you hard-link ...


11

I can't help feeling that if you can't answer this question yourself, then you don't know what you are going to use the data for even when you have it. Maybe if you think about what data you actually need it might help? Do a little role playing where you put yourself in a position where you actually need to make use of this information in different ...


1

If you're only able to do one, I'd go with email. Mobile number is very personal to a lot of people; they are concerned about spam calls. Sure spam emails are a problem too, but they don't demand time in the same way as a phone call. Also Facebook is a well-known name - providing your phone number to them will be regarded as 'safer' than to a smaller, ...


2

I assume you’re designing a public facing web site, where your target is to let new users register to be able to access content. And you want to decide whether to use Email or phone number when they register. If your goal is to get as many users as possible, my recommendation would be to use both. Some users like to register with their Email address and ...



Top 50 recent answers are included