Tag Info

New answers tagged

3

The law in the EU states that a service provider should not disclose ANY information on an individual without an explicit consent from that individual. Whether or not one is a member of a particular site falls into 'ANY information'. As such, a website should not tell anyone whether the email address exists is in the database or not - doing so will reveal ...


1

I would find this annoying as a user: if you make a mistake in typing your password most often than not it's due to having added or omitted one character, and this is especially frequent on mobile apps, so being able to at least doublecheck the entry before sending it is quite useful. Also, I doubt it is really needed - if someone is trying to look over the ...


3

If you're talking about while the user is typing, I would highly recommend against this. The user will think they are mistyping the password since the mask won't match what their trying to type, and it will cause frustration for the vast majority of your users. The "shoulder surfing" risk is not worth the UX pain (especially if you are enforcing a minimum ...


0

This is a very interesting, albeit micro scenario to consider. In the case that you provide, I'm a huge fan of account creation only after a shopping cart purchase has been finalized. This can even include an action/request by the user before the "purchase" button is hit (such as 'please create an account for me after purchase' checkbox next to an ...


0

I think the scenario you describe is very unlikely to happen. The user will finish his current goal at the eCommerce, before he attempts to change other passwords. It is true though, that the password strength indicator will be a distraction that will consume user's attention and may also cause anxiety. But this is a matter of trade-off between enhancing ...


0

Rather than Showing them Password Strength. Show them in this way. For low password strength-----"Anyone can steal and guess your password" For medium password strength----"Brilliant people like James bond can guess and steal it easily". For Strong password ----- "Even god can't guess or steal .Good job"...Something like that :)


0

Yes,couldn't agree more . Users like to achieve more thing doing less operations in any field as a matter of fact. But I tried to solve the problem with respect to the requirement , that has been mentioned in the question.


1

Even though you will save space by combining both fields onto a single page, I would be inclined to present each field on it's own screen. The user elects to pay The user is prompted for password - the user enters password The user is prompted for OTP This way each page could have it's own intro text and help links if required. Otherwise you would need ...


1

When they enter all their details and click on pay, show them the password field as well as the OTP field. At the same time you should send the OTP to their mobile. When they click confirm or submit, they should be able to do the transaction. You are reducing the number of clicks. You are doing all operations on a single page. No complexity for the user ...


0

Don't The user wants to give their credit card info and delivery address (if applicable) and nothing else. Ecomms on mobile is already bad enough without these extra steps; think how simple a real-world transaction and then go back to this system and you'll see what I mean. you might find this link useful http://baymard.com/blog/mobile-checkout



Top 50 recent answers are included