Tag Info

Of course it will turn away some visitors! Reasons When somebody needs to register in order to use a site, he's asking himself additional questions, like: Which informations do I have to give? How much time will it take me? Which value does the website give me? Is the value more than the effort I need? Can I trust this site to keep my credentials secret? ...

There are as far as I'm concerned two key issues to address when using a SSO (Single Sign On) -concept. Accessability: The sign in/registration page should clearly show that the users may sign in using their Facebook account. Credability: The button/link in addition to the overall page should convey credibility. There is an A/B-test with the use of ...

The most common and accepted button has been "Log in" button. It's what you see the most and what most people will feel "comfortable" using. Facebook lists that button on their developer pages - http://developers.facebook.com/docs/reference/plugins/login/ http://developers.facebook.com/docs/guides/web/ I think from an aesthetics point of view, the ...

Though using a gold border is nice (and I don't think you should remove it) it may not be very obvious to people. I assume that you want it to be quite noticeable in order to get more people to upgrade to a premium account. Is there anywhere that you show more info about the user? For instance on ux.stackechange the users name, rep, badges are shown next ...

If you take a look at this StackOverflow question, you can automatically merge accounts that use the same email address as their Facebook accounts. Doing this would be the right way forward in my opinion, as it requires no change to the already existing UI. However, it might be an idea to tell those who are logged in through Facebook that they have an ...

Mapping is the key to get a user to recognize a service. The credibility and recognition of Facebook is lost if the web site uses different fonts and different colors for the Connect- or the Login-button. This doesn't mean that the web site using the correct Facebook style is more credible, but the user will feel more secure. Take an example from the dark ...

I like Groupon: and Digg's log in is nice as well: They both ask for permission when you click: And then you click and you are done! I am all for using this whenever possible, Open ID as well. Here are a few Screen Shots: So as I am typing up my examples I found a great article on mashable http://mashable.com/2009/01/12/facebook-connect-implementations/ ...

friend.ly has a ridiculous implementation of Facebook Registration. Their homepage displays a small box containing form fields that have been pre-filled with your information if you're already signed in to Facebook, such as your name, date of birth, photo, home town, etc. All you do is click "Register" and you're in, and it knows who your friends are and ...

Reasonably clean UI. Brewery may not be meaningful for most people. What percentage of Budweiser drinkers can spell Anheiser-Busch (even if they've heard of it)? Even fewer Singha beer drinkers (most popular beer in Thailand) know of Boon Rawd brewery. If brewery name is an important piece of data, auto-detect it based on the beer name or offer it in a ...

And if you decide to use FB connect you have to offer a normal signup process, too. There are users out there who do not have a Facebook account or have one but don't want to connect their account to other sites. Since there is no standard way many companies offer a range of login-in options from FB to Google and OpenID like they do here on Stack Exchange.

My advice is avoid unless you absolutely have to, for example, for security reasons or validation. Like Giraff says, it places a barrier between the user and your content, an opportunity for the user to click away. FB etc fast sign ins certainly make life easier but you still have to convince users why they should sign up in the first place..... I must ...

People will not signup to a bad site simply because it supports Facebook/Twitter/Google's authentication mechanism. (I don't know your site so this is not implying anything about your site... :) ) That being said, I think it is safe to leave the FB Connect buttons on the user registration page because at that point they've "expressed" an interest in ...

You could just show a simple table with explanations of the state of these social tools and options to change their state. By the way, this is something I haven't seen in action yet, but may be a real benefit to the user: Show how much is shared on average daily/weekly/monthly (depending on how frequent: for example > 10 per week = show daily average). ...

A slight change in wording should do the trick here. Since the accounts on other services already exist, rather than Sign up (which generally indicates creating a whole new account) say: Sign in with Facebook Sign in with Twitter Sign in with Google Then for creating a new account on your site, Sign up with xyz.com

Everyone knows the design of Facebook, then the best way to recognize it for an user is to use the original. Not only that, a user may also be more psychologically involved recognizing something they already know. Many use their own design for the button and I think it is less effective than the original one.

When they register for the application, they should be (depending on your wording etc.) agreeing that their posts on the site will show their facebook name. So they have already given permission to post with their name, and if from that point they post a comment, it's reasonable to show their name when they post. I'm not sure of the technical feasibility ...

This is a very vague question that actually assumes that the user has a reason to connect your site/app with Facebook - we don't actually know why you want to use the feature - is it mainly for logging in or account creation? Or are you mainly using it to access other data like friends (are you trying to help the user connect with friends that they already ...

I like the sites that present the option as two sides to a box. Sign up for an account or sign up using Facebook, Twitter, etc. (using the social icons). I can't think of an example right now. But I think this is the best compromise for the UX Sign in to XYZ.com Or Sign in using Username Facebook Twitter ...

I doubt there's real data available because the success of the button would be inherent to the success of the website using it. Anyway, when choosing this button I think there are 2 main things that should stand out: The Facebook "F" everyone knows so well, and the white font on a blue background. The 3d and 4th are not recommended in my point of view, ...

I advice to have a login for comments, forums etc (both with your own and something like facebook-connect) but for if you want to give them their own experience (as long as this doesnt consider to much personal details) you can just store the information without requiring them to log in. You can generate a new id for every visitor and give him/her a cookie ...

I'd ditch the 'Brewery' selection completely. The name of the beer is probably unique within a country (so maybe a country selector would make more sense). If it's not (eg the Czech Budweiser and US Budweiser sold in Europe) give both options. What's going to happen if the beer isn't on the predictive text list ? (There must be a heck of a lot of ...

Yes, it seems very straight forward, My only comments are the following: Its not clear if the beer or brewery is a required field. The action of posting is a bit disorienting. Its hard to tell what happend or if it worked. Users like positive reinforcements. When you post here on stack exchange there is a orange highlight which then fades away to show you ...