Sunday, September 24, 2017

registration - Should we restrict signup for a service to Facebook accounts only?


There are obvious advantages to limiting sign-ups to a service like Facebook connect - getting a name, age, avatar, etc. without the annoyance to your customers of asking them to fill it all in.


We are currently considering this, but there are some good arguments for using other services as well - such as Twitter, LinkedIn, Google, etc. I can even think of some very good reasons (privacy being chief amongst them) to still keep our own sign-in.


The issue then is that giving people too many options is not a good UX.


Our target audience is subject specific (architecture, language learning, etc.) so we can't predict our customer audience very well yet.


What would you use for sign-ups and why?



Edit: I need to add that our application is targeted at mobile use, so screen real estate is also a consideration in showing many options.



Answer



Facebook only? Don't do it! I would always give people the option for maximum chance of sign up. Sign up forms that allow for your own sign in and using another account don't have to be complex, although many do seem to be for some reason. Digg is a good example of one that keeps it pretty simple.


You already said you don't know your customer audience that well - so why throttle it with such apparent inflexibility from first sight.


enter image description here


No comments:

Post a Comment

technique - How credible is wikipedia?

I understand that this question relates more to wikipedia than it does writing but... If I was going to use wikipedia for a source for a res...