News for hackers. Stuff that matters.

A comment on Ask HN: Conversion rate increase with a Facebook sign-on?. Parent comment

Re:Ask HN: Conversion rate increase with a Facebook sign-on? by ebun on Wednesday August 11, 2010 @12:16AM (#1593805)
"I'd wager that many startups don't implement Facebook signin because of the engineering overhead that could be spent on sexy new features."

How much time is really spent integrating FB Connect?

[ Parent | on HN ]
Re:Ask HN: Conversion rate increase with a Facebook sign-on? by fookyong on Wednesday August 11, 2010 @08:43AM (#1594501)
The fact that it requires learning a new API makes it a non-trivial feature, engineering-wise IMO.
[ Parent | on HN ]
Re:Ask HN: Conversion rate increase with a Facebook sign-on? by ebun on Wednesday August 11, 2010 @01:17PM (#1595310)
I wouldn't have deemed it trivial, but the part I quoted made it sound like the associated workload was pretty heavy.

I haven't looked into the API or what it takes to integrate it, but I assumed (bad habit, I know) it wouldn't necessarily be rocket science. Aren't most API's relatively simple to use compared to the actually building of an app?

Plus, if it causes a huge increase in users and tire-kickers, it seems an app would get more chances to show off their sexy features anyway.

[ Parent | on HN ]
Re:Ask HN: Conversion rate increase with a Facebook sign-on? by msencenb on Wednesday August 11, 2010 @02:13PM (#1595495)
After looking at the docs it doesn't appear to be incredibly hard.

I think the most non-trivial thing would be integrating with the current site sign-on. Issues such as an existing users that decide to sign on with facebook (which is linked to a different e-mail address) could become a problem on the backend.

[ Parent | on HN ]