5 ms·
Ask HN: Requiring FB Connect, Will This Kill My Startup?
I'm curious what other people's experience has been using FB Connect as a sign-in option for their web apps, especially those that use it exclusively.
It seems that many people, even "tech aware" younger users, don't understand FB Connect and may be suspicious of it. This makes me worry about all the majority of potential users, who on average will understand it much less.
Any idea what % of potential users will automatically refuse to use a service if it requires them to login with FB Connect?
I ask because the startup I'm launching soon will require users to login using their Facebook ID. I'm not worried about internet users that don't have FB, because they're not likely to want to use our site anyways (its a video chat application).
Also, many sites allow you to login with your FB ID, Twitter handle, Google account, or to create your own account. For my startup, there are specific reasons why offering multiple forms of login won't work, so we've opted to use FB.
Cheers.
- Towle_ 16y agoI personally wouldn't sign up for anything with FB connect, but who cares? Go for it. If you really must have just one form of login, then FB is by far your best shot. If it doesn't work, nothing else would have.
- onwardly 16y agoI'm curious what your rationale for this is. Assume that from the landing page you can be confident that none of your personal information will be shared and that the application will never post anything to your wall, etc. What's the worry? The whole point of FB connect is that you don't have to create accounts on every website you visit, while still enjoying the enhanced functionality that comes with having a "profile" on each site. Anyways, I care because if 90% of potential users leave the landing page because they don't want to use FB connect, then that's going to pose significant problems for us! Regardless, we are "going for it"!
- Towle_ 16y agoAssume that from the landing page you can be confident that none of your personal information will be shared and that the application will never post anything to your wall, etc. I wouldn't assume that. By default, I would be skeptical. I can't just trust you because you say you're trustworthy. That's why I don't use FB Connect. Well, that's half the reason. The other half is, I don't want FB to have a profile of a bunch of sites I'm a regular user on. I want to be able to say and do things on those sites that I wouldn't do on FB. Like this: http://news.ycombinator.com/item?id=1641266 http://news.ycombinator.com/item?id=1641266 edit: Good luck! Maybe I'm an outlier and it won't hurt much. But like I said, it's easily the best choice of those you have available to you.
- onwardly 16y agoI understand where you're coming from, but it also sounds like you share some common misperceptions about FB Connect. For one, before you login with FB Connect, it tells you exactly what the application is requesting your permission to do. If the application wants permission to post to your wall, FB tells you upfront that it is requesting that. So you don't have to believe my words- when you click to login you'll see that the only information requested is just your basic profile information. Nothing else. Regarding FB having a profile, I don't quite understand this. For one, FB doesn't know what you're doing on my site. All it knows is that you signed into my site. But Facebook can't really "do" anything with that info. It can't post on your wall that you logged into my site, it doesn't have access to any of your activity on my site, etc. Thanks for the good wishes. I don't think you're that much of an outlier, but I think a lot of that has to do with how poor of a job Facebook has done explaining Facebook Connect. I'm expecting that over time, people will increasingly understand how it works and be less suspicious. Maybe.
- arn 16y ago"it also sounds like you share some common misperceptions about FB Connect." I suspect it's not just a "common" but overwhelming misperception. In fact, before reading what you wrote here, I didn't know that's how it worked. I am an intermittent/casual facebook user, and use it only for real personal connections. As a result, I never log into any website or iphone app that offers facebook login, for exactly the concerns listed above. The rules also seem to change over time, so just to be certain, I won't use it.
- Towle_ 16y agoarm: The rules also seem to change over time... This is one of my main concerns, onwardly. While I acknowledge that I as the user must give permission for the application to access different kinds of information, FB also changes their privacy terminology/definitions and user agreements too often for me to feel safe about it. While I'm confident FB themselves won't sell users' data to third parties because it's not worth it to them from a risk/reward standpoint, I can't be sure about smaller websites who'd be capable of getting away with it if sneaky enough. One last thing: I think it's important to note that I honestly wouldn't even look at what information is being requested. I would just hit the back button if FB Connect were required. If others are the same, that's a big barrier to have. But I think I've seen sites immediately jump to the permission request stage, which would eliminate that barrier. If the user is reading the request where they otherwise wouldn't, your overall stats will be much improved. (Maybe you're already doing that. If so, just ignore me and my ramblings. But I haven't seen all that often.)
- jusob 16y agoFor a website, I offered login with Twitter, Facebook or custom username/password. I thought people would take the easy way, and use their FB login. Wrong! 90% of them chose the custom login + password.
- udfalkso 16y agoI'm curious what your audience was like. Young? Old? Tech Savvy? Did your site focus on something potentially embarrassing if it would end up on your FB profile?
- jlgosse 16y agoFrom my experience the average internet user is quite afraid to give up their Facebook credentials to a random site.
- _delirium 16y agoYeah, I think FB Connect hits right at the time that anti-phishing education has finally made people super wary of cross-site types of issues. They've had repeatedly banged into their heads: if the URL bar doesn't say example.com, don't give any of your example.com-related information to it, no matter what story it tells you! Of course, FB Connect doesn't actually require you to enter your Facebook password into a non-Facebook site, but I can see how people would be scared off. Using your Facebook credentials for something you didn't reach by typing facebook.com into the URL bar yourself feels at least superficially just like the sort of thing all these campaigns have been about...
- tomjen3 16y agoWhat was your reason for not just using openid? It is a standard, gets you a wider user base and the services already mentioned support it too.
- sqrt17 16y agoMost people who would have an OpenID-supported authentication method wouldn't know that they do or how to use it. A big "use Facebook/Google/Gravatar/whatever to log in" button makes it easy even for the people who don't have any OpenID background.
- JoelPM 16y agoI don't have a Facebook account (and I refuse to get one), so in the unlikely event that people like me are the sole target group of your application/website, yes - requiring FB connect will kill your startup =) But like I said, it's unlikely.
- onwardly 16y agoTrue. For one, most people in our target age demographic (say 16 - 34) do have FB accounts. The other assumption is that if you don't have a FB account, you're less likely to want to talk with strangers over videochat.
- NinetyNine 16y agoI'm 20 years old, tech savy, and I'm weary of facebook connect simply because other cross-site facebook tools have been exploited before, particularly the like-button click-jacking worm (Troj/iframe-ET?) which has filled my own feed with spam messages. I removed my facebook account a few months ago, so I wouldn't be able to use it anyways, but if your site doesn't need real-person verification, then don't even bother, a lot of users prefer a nick over a name, and a sign up form isn't as big of a deal as potentially giving away your facebook credentials to a spammer using an unknown exploit.
- pjy04 16y agoStop wasting your time and doing fb connect. Just do the traditional method and test your idea fast and easy. FB connect will slow down your development and make it complicated. FB has changed so much this year alone, you'll have to change each time they add something new.
- deleted 16y ago[deleted]
- btmorex 16y agoI've already skipped a few services that sounded interesting because they used fb connect (I do have a facebook account). So, to answer your question, if enough people are like me, then yes it will kill your startup.
- Locke1689 16y agoUse OpenID. I never give my user information to another site, if possible. OpenID is the most portable of those implementations. Edit: Ah, didn't see at first that you can only have one form of login. I guess you can use FBConnect (and that provides a significant user base), but I won't be signing up...
- tobtoh 16y agoI'm a heavy FB users and always opt to create a separate login account rather than use FB Connect. My understanding of FB Connect is probably flawed, but I don't trust FB to use whatever linkage/info they get from the login with my best interests at heart. I also don't trust any app that requires FB connect as, rightly or wrongly, my suspicion is that any app requiring FB connect is out to spam my newsfeed and my friends news feed like Farmville does. If the only login method is FB Connect, I just move on.
- b0o 16y agosame here. Facebook connect sucks. If it's your absolute best login option, then GG to you sir, you failed before you even started.
- sqrt17 16y agoEven though I may use FB connect to sign into a site, I (and I guess many others) would be deeply suspicious of any site that exclusively uses FB connect. At the bare minimum, offer FB, Google and Twitter so people don't feel like they're coerced. (And you'll be surprised how many "not likely" people use a decent application if it's useful and you don't send them away). My guess is that 90% of potential user will go away when you force them to use FB, whereas 70-80% of your potential user base will still find something not to like when sign-in is not a problem. (i.e., think about the conversion ratio from people who learn about your site to people who either go "ooh, I'm going to try this out" or "hm, looks interesting but whatever" - people are often walking a thin line between these options and shifting the line by making trial and sign-up as easy and convenient as possible will get you more conversions). Otherwise, if you're willing to put your soul into FB's hands, do the full monty and structure your app as a facebook app. If you don't think that would be a good idea, think about why you're only targeting facebook users. (And do remember that "facebook demographic" and "actual facebook users" are very different things).
- onwardly 16y agoThis comment, like many others, is pretty critical of using FB Connect exclusively, which is something I understand and why I posed the question in the first place. It may help to provide a little more context. The reason that FB Connect is used exclusively is to solve the pervert problem that has plagued videochat applications. The FB account is used ONLY to track users, and on the landing page we make it very clear that we never reveal your identity to anyone and that we never post anything to your wall or your friends' walls. We use the FB login so that if you are reported for misusing the site we can block you permanently. The thinking is that if we just allow you to create a new account or login with different accounts, then the pervs will be able to continue to access the site even if they are blocked on one account. On the other hand, I'm getting the sense that this could be a big problem for legitimate users. Perhaps having multiple sign-in options would be OK, assuming that if you're a perv you'd be wary of signing in using your real account info, and that you'd really be going out of your way to be a jackass if you waited til one account was blocked before and then signed in using another account. I'm surprised that the HN community seems more averse to using FB connect than I expect most normal users are. Either that or people that are critical of FB Connect are more apt to respond to this. Lots of food for thought though. Ultimately, the question is whether offering multiple sign-in options dilutes the security feature of being able to permanently block those who misuse the site. While it does dilute this slightly, I'm starting to think that the trade-off might be worth it if only allowing a FB sign-in is so repulsive to so many...
- andrewf 16y agoFirstly, Facebook really do "move fast and break stuff," and dealing with their APIs is both slow and aggravating. The app I'm working on has a lot of social functionality, which is why I'm bothering. (You may have similar plans). I've never implemented Google account login, but if I didn't care about the social stuff I'd be leaning towards that. Are you doing a "hard launch" with lots of PR, etc? If so, I would be thinking very hard about the risks in being FB-only. A lot of people will never visit your site again. If not, then you have more freedom to experiment. I'd be inclined to go with my gut, but: metrics, metrics, metrics. From day one you should know how many people are being pushed to authorize your application to know about their Facebook identity, and how many of them are coming back after clicking the "Authorize" button. Facebook has a dashboard which I haven't investigated, but it may be good enough for you to avoid implementing your own metrics.
- onwardly 16y agoThis is a good point. We are in fact doing a "hard launch" as a result of the need for a critical mass of users. Its a videochat website, and if noone is there then you'll just leave. As I mentioned in another comment I made just before this, I'm certainly reconsidering the decision to do FB-only. The main thing I want to stay away from is allowing users to create accounts. We don't want pervs to be able to get booted off and then just quickly create another account. But it does seem to make sense to offer Google, Twitter, and perhaps another sign in option.
- gaiusparx 16y agoPersonally I would not use FB Connect unless you're already a name I can trust. If I'm not wrong, when you use FB Connect, you can capture only the user id. The disadvantage is you are not able to build a meaningful customer database, but this also depends if customers info is important to your startup. Secondly your startup will live and die with Facebook. This makes sense only if your startup is a Facebook app.
- dmc 16y ago> If I'm not wrong, when you use FB Connect, you can capture only the user id. The information you can currently 'cache' from facebook, is called basic information and currently consists of: > user ID, name, email, gender, birthday, current city, profile picture URL, and the user IDs of the user’s friends who have also connected with your application. You can also easily request other information, such as email address, without any additional dialogue box. I'm not sure whether most users would realize that this additional information is being shared, or not.
- kvogt 16y agoFb connect on main signup form, regular signup a click away: signups down ~15%. Well-designed main signup form w/ fb connect as an option: signups up 8%. 30k new users per day, data statistically significant. Ymmv.
- jonnycat 16y agoHave you been able to measure engagement of the FB connect users vs. the regular signup users? It's been said that while it's easier to get a user to sign in with FB connect, those users are less likely to stick around and do anything meaningful on the site.
- motters 16y agoIf your site requires Facebook Connect for login, I will not use it. There's no reason for it if your site is not directly affiliated with Facebook, and it may result in privacy issues. Personally I think as soon as a viable alternative to Facebook exists I will stop using it anyway.
- abraham 16y agoUse FB Connect or RPX. Please don't make me create yet another user account.
- alexkiwi 16y agoMy experience is that it works as an added bonus, but shot our conversion rate down when we tried it as the only way to login. Good luck, your going to run into some fun facebook errors.
- stoney 16y agoUnless I specifically wanted your startup to be putting stuff into my facebook feed, I personally wouldn't log in to your (or any) site using a facebook account. I'm a bit paranoid about the potential for 3rd party apps to publish stuff to my facebook account that I don't want them too - the whole facebook privacy thing is just too murky (I don't really understand what you could or couldn't do if I logged into your site with fb connect), so in general I just play safe and keep facebook separate from everything else.