Tag Info

New answers tagged

0

I wouldn't overthink this problem -i.e., don't wait around for a study that shows the bounce rate at the point of entering password. You can trust that if people are willing to enter a password, they will not change their minds because you've added a few security features. It is safe to assume that people have their go-to password that meets most ...


0

I think the size of the UX changes should reflect their scope. If the developer option is something like "now you can change the background color!", then the "normal way" is totally fine, as it's not a big change. Option 1 makes sense if the "Developer's area" is totally separate from "Profile options", and has a similarly scope for changes. This seems ...


2

In most cases I agree that it is the better option to minimize the number of steps or actions the user needs to go through. Accepting a ToS is a different thing in my opinion. Even though most people probably doesn't read the ToS anyway I would consider it too important to "hide" the action. Unless you make the text below the Sign Up button VERY visible I ...


0

In addition to the reduction to cognitive load - It might sometimes be a technical limitation. Many sites take you to completely different area as that separated area might be run by a completely third party site. Contests and Loyalty on some Publisher properties can run this way. That may partially answer the back button dilemma. The other half is ...


0

Here I'm giving a try- there are many dependencies the service provider would validate while anyone sign up for them. 1. Correct information 2. Security 3. Avoiding spam From user experience point of view during signup, user has to depend upon his cognitive load. they have to recollect many things and also try different options. So to reduce this load, ...


0

If a user is directed to a sign up page then the only thing available for the user must be to sign up. When it comes to user experience the user must get what he/she is looking for and what he/she has come there for. Keeping other options/ information on the page may not only be less productive but may also host as a distraction for the visiting user. Hence ...


0

What is the purpose of the authentication? Are you collecting e-mail addresses for a marketing campaign? I see another flow with your potential alternative User enters email and hits submit I read this as User enters fake email foo@bar.org and hits submit User sees content So the user can effectively view the content without registering


2

A book I really found helpful for this topic is Seductive Interaction Design. It deals with the many ways we can keep the user invested in our content while we get the information from them that we need. Studies show that people who have made a very small commitment are psychologically more likely to agree to a bigger (and more inconvenient) similar ...


1

I assume that you want to increase the registration rate, so I suggest to keep only the necessary fields that will enable you to communicate with your users following a successful registration (for example in order to upgrade their account). It's known that as the number of form fields increases, conversion rates decrease-see the graph below. I recommend ...


0

Its basically as per your need. But yaa if you're asking for suggestions, then personally I feel you should for a slide-down panel. This because if the site is been accessed by smartphone users or probably tablet users then slide-down will be a better option for the users. Where as lightbox would be a cumbersome thing for them to open and see. Most of the ...


1

The are several methods up implement this, utilised by many high profile sites today. Invitation Only, pyramids Google did this by providing limited invitations to phase 1 users. For phase 2 they provided those users with limited invitations so they may grow the database but only after a certain usage time is met. Incrementally provide access When ...


0

In recent apps I have been trying a bit of a new format for keeping the flow of a user's registration in one piece: User fills in form. As soon as they enter an email address, I validate it and email a confirm code using ajax. Before finishing the registration form, the code must be input. Once they click done on the form, they are registered and verified. ...


0

Like other people suggested, it's a very good idea to let user's explore your app before email verification or give up email verification at all. But if you really need email verification, you may use the mobile's capabilities to improve the user experience. Fill in sign up form. Done. (Available features are still restricted.) Your app checks emails in ...


0

Short answer: Registration may take place on another page and that will be fine, if this is well-thought and supporting organizational objectives. Detailed Response: What is a landing page? A landing page is the page within a website which is meant to receive your visitor directly and entices him to do something further. Thus it acts like a door ...



Top 50 recent answers are included