|
I want to know if facebook connect button should be glaring at users straight from the homepage, or only at the login and register pages when users actually need to login or signup? What does each of the two choices bring in as a plus and minus to the table? |
||||
|
|
|
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 have, but within your app?). Otherwise, the responses come - "use a dropdown" etc... I suggest tackling issues like this from the perspective of flow- e.g. when (if at all) is this feature most useful to the user. |
|||
|
|
|
A short answer: Yes. With a very valid reason.Your users are not getting to an actionable item on the homepage.The action happens after login (unless that assumption is not true in your case). Facebook connect is just another way of signing-in. Adding that option for a later stage is creating another round of clickable actions before the actual action. In order to avoid a huge facebook connect button, using a drop down with the sign-up would do the job. |
|||
|
|
|
I've found this blog post very inspiring. In general I suggest to encourage the users to sign up with you and maintain the control over your users. |
|||
|
|
