On Jan 20, 2010, at 11:30 AM, Michelle Rajunov wrote:
Hi all,
The site we're doing is a contest users enter and submit photos. It
requires users to be over 18, or if they are between 14 - 17 they
have to go through a consent flow.
I got a question from a designer about what would be better in
>From a strict UX standpoint, Ortiz has it exactly right, age range
options are simplest. When it comes to additional data uses, a short
explanation, or "why we ask" is required (for user satisfaction) to
get more specific date (mm/dd/ is simplest.)
. . . . . . . . . . . . . . . . . . . . . .
birthdate and drivers license = all access... through in the social and it
gets even scarier
On Fri, Jan 22, 2010 at 4:23 AM, Jarrod Lombardo wrote:
> Wow, I'm surprised by the number of people that consider birth date
> private information. Since one's birth date and much of one's
> address hist
Wow, I'm surprised by the number of people that consider birth date
private information. Since one's birth date and much of one's
address history is a matter of public record (in the US at least)
there's basically ~0 risk in freely giving out your birth date.
A text entry form that shows how to in
I wholeheartedly agree with Sean Gerety and Michelle Larsen that birth
date is private data and should not be requested, unless absolutely
legally required to do so to that degree of specificity. I personally
use a made up birth date for these types of requests (still in same
age range). I even ta
Senior Interaction Designer vacancy at Telefonica I D Madrid (SPAIN).
We are looking for a highly motivated and talented Senior Interaction
Designer to join the team of Interaction Designers, Visual Designers
and Researchers. Designers and researchers work in collaborative
teams with project leads
I've done a variety of contest sites across many age groups. The
difference between 1 and 3 fields isn't going to matter to most
contest-doers. I say this because their motivation to "win"
outweighs the need for "speed" of a form. On most sites you will
see that you're average contest participant i
I remember a situation where the 18YO were the main audience and the
14YO were added at the insistence of an overzealous marketing
person. From a product point of view, support the 18YO first.
In any case, why not:
I am ( ) 18 or older, or ( ) over 14 and my parents agree to this
then unhide
As a user, I almost always abandon a form that requires my birth date
without any apparent legal or governmental need.
One's birth date is up there on the list of most-private private
data, and I immediately question how and to whom my information may
eventually be passed or sold. I don't necessa
Just curious, but why three selections and not a date picker or text
box where one can key in MM/DD/?
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Posted from the new ixda.org
http://www.ixda.org/discuss?post=48490
Just to clarify, the contest will last around 40-50 days, but we are
looking at ways to extend site use afterwards. Also, the prize is
significant, and will require real verification of user age, which is
a big incentive not to lie (I suggested putting a 'notice' above the
dob/age field highlightin
As a user, I almost always abandon a form that requires my birth date
without any apparent legal or governmental need.
One's birth date is up there on the list of most-private private
data, and I immediately question how and to whom my information may
eventually be passed or sold. I don't necessa
Luke W's Form Design book says to use smart defaults and that a good
solution would be to ask people to explicitly select the month, day
and year they were born. Also let them know why you are asking for
this information.
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Posted
I think the three selctions are a waste of time if you are not
planning on using the data collected for further use (e.g targetting
users for another marketing campaign based on their birhdays)
But if your not sure what you will do in future, its safe to collect
detailed info
. . . . . . . . .
There is a difference between the two that you might use in the future..
Age: is easier to fill, faster. But.. if you need the age of this user in
the future, you may do a mistake.
Date: not so easy, not so faster. But.. you can calculate de age of the user
forever..
On Wed, Jan 20, 2010 at 9:
Assuming the business and legal case stands up to accepting either,
you could offer users the option to denote their age status (ie,
above or below 18 years) or enter their date of birth. This would
give you the chance to offer value to customers if they enter their
DoB (eg, "if you want you can te
I would not consider terms of use (and legal issues) would be
justifying birth date entry.
In this concrete case the actual data you want to collect is not an
exact BIRTH DATE but AGE RANGE. So, I'd prefer age-range choice
(agree to Sean)
Of course, this question should be asked at the top of th
You could design a smart UI where there are three options;
I was born:
[18 or more years ago today]
[14 to 17 years ago today]
[I'm not of age]
That way the user just needs to select one option instead of facing multiple
entry fields.
Eduardo
_
Another thing to consider is that birth dates are specific and people may
not want to give you the date because of security reasons. I'd recommend
age or even age ranges.
Cheers,
Sean
On Wed, Jan 20, 2010 at 7:06 AM, jodah jensen wrote:
> All things being equal, the fewer data entry points, th
Date of birth can be handy in the future because you always know the
person's age. If you run another contest, you can invite just those
over 18, or if they're signed in you'll know what flow to take them
through.
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Posted from the
All things being equal, the fewer data entry points, the better.
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Posted from the new ixda.org
http://www.ixda.org/discuss?post=48490
Welcome to the Interaction De
Hi all,
The site we're doing is a contest users enter and submit photos. It
requires users to be over 18, or if they are between 14 - 17 they
have to go through a consent flow.
I got a question from a designer about what would be better in terms
of UX for the sign up form - asking the user for:
22 matches
Mail list logo