Most of you are familiar with forms that highlight required fields. The problem with that is that most fields are required, so you end up having to highlight everything creating a clutter of asterisks or sub-labels.
I want to share with you a different approach that is much more minimalist. Feel free to chime in and let me know what you think.
Hey all, have any of you had successful experiences with automated, temporary passwords being generated during the user sign up process?
I didn't read anything about this in Luke Wroblewski's work and am looking for some insight. Our demographic is composed of many people in their 50's and 60's. I am looking to increase the ease of the signup process.
I'm currently working on a revision to a checkout process in which we're debating the pros & cons of pre-populating certain fields.
The application allows users to select an item for "purchase" and pledge an amount related to the value of that item. This means they can in fact pledge more than the stated amount for the item, or the exact amount of the item. They obviously cannot pledge lower.
The debate is such:
Do we pre-populate the form field with the amount of the selected item or leave it blank to encourage some percentage of greater pledge.
In our work, everyone (stakeholders) wants to use a graphical button for their CTAs, often asking for multiple such buttons on a single page. The notion is that these will drive a higher conversion rate... ON THOSE links. (These are not form submits, remember.) A proof of concept was done late last year to test the effectiveness of buttons vs. links on a particular page. Here was the scenario:
I have a quiz where people fill out 15+ questions to find out what kind of traveller they are. My client would like to ask them for their postal code, so that they can ultimately send people information and offers that are customized to their traveller type and location. They would also like the postal code to validate the geo segmentation research about the traveller type differences by location.
Quiz respondents are not asked for their full mailing address. They have an option to opt in to receive further information by providing an eMail address.
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:
- their age with a text input /or select, OR
- their date of birth, with 3 select fields [day, month, year]
Just wanted to get some input about your experience with this.