New answers tagged

0

I'd be tempted to go with this idea. So long as it does not introduce significant risk (which is usually an area outside the remit and expertise of UX). When I'm faced with a design idea that I have no experience with such as this, I always do 2 things: Articulate the issue, its potential benefits and disadvantages, and ask for it to be added to the ...


0

Require a phone number. Think of your persona, Harry. (Taking some liberties here by making up your persona for you.) He is married, with two young children. He already has a girlfriend on the side, but she is getting demanding, so he wants to dump her, but not until he has identified a suitable replacement. He downloads your app and registers for the ...


1

Having seen first-hand what un-moderated map pinning results in, there are a couple of ways that users will try to abuse your system: Using pins to draw or write on the map. This is easily solved by simply limiting the number of pins available to non-registered users. Once they reach their limit (anywhere between 1 and 5 - just below whatever you're ...


1

What if you could have your cake and eat it too? Here is what I am thinking: Allow new users to drop pins on the map without forced registration. Trigger an optional login/create account request after they've dropped a few pins and am feeling proud about their work. The request must explain that pins coming from anonymous users are not immediately ...


1

Your industry or company may define any regulatory or other requirements you must be able to support, such as requiring a user's permission before you can log in as them. But speaking from a technical perspective, having built several systems like this before, here are some features that I have found helpful: Ability to log in as a customer is a controlled ...



Top 50 recent answers are included