I have like/share buttons on my website and am not currently using an appid. Finding information on whether this is a necessity for the above configuration is difficult to confirm. When going through the Facebook app "create" forms, I'm really confused by a lot of the requirements as it seems to be more focused around actual apps rather than websites, which login via fb etc.
In the past I have created an app for one of my other websites and I don't believe there was any verification/submission process at this point (about 2-3 years ago). Reviewing my old app configuration now I can see that it is not "live" - does anyone know whether Facebook implemented this submission process in the last couple of years, and then de-activated any live apps that were created prior to this?
I now want to setup a new app for my new website and I'm unsure what the different 'action types' mean and what I would need to simply use like/share buttons on the website. Could someone give me a quick run down of what I'd need and what they are?
Any other info/tips people can provide would be greatly appreciated. I'm finding that the like/share DO still work without the app, but sometimes the share button doesn't work properly (I have a feeling this is something to do with the app).
Thanks
If you are just using the Social Plugins, you don't need to have a Facebook App ID.
If you want more integration, it will be required. Creating an App ID is like registering your App, wether an iOS or Android App or just a website, so that you can make Graph API calls for it.
The easiest way to register your website is to go the quickstart: https://developers.facebook.com/quickstarts/?platform=web (or https://developers.facebook.com/apps). There you can type a name and follow the steps.
You can then follow the "Sharing best practices" (https://developers.facebook.com/docs/sharing/best-practices#tags) on how to use the App ID. For example, by including an fb:app_id meta tag on your pages.
There is a review process, since last April, but that is only needed if you use permissions for your App. If you just use the plugins, that is not needed.
Can you explain more what is exactly not working?
Update
The time you create a page the Facebook crawler does not know yet what the Opengraph data for that one is. This will happen after the first share, but if you want to ensure it is correct from the first share on, you can force a re-scrape.
This section explains how that works:
https://developers.facebook.com/docs/sharing/opengraph/using-objects#update
When an app triggers a scrape using an API endpoint This Graph API
endpoint is simply a call to:
POST /?id={object-instance-id or object-url}&scrape=true
I'm working on some new features for a CMS, and I'm having trouble finding the information about how Facebook interacts with other websites. If turn key solutions exist for this I'd love to hear about them, but I'm basically just looking for pointers to documentation of how this stuff works behind the scenes. Including php, wordpress, and drupal since those are the base technologies I'm working with, but other platform solutions are welcome.
When you paste a URL into Facebook's "What's on your Mind" box, Facebook will automatically fetch a short page description, as well as a list of possible thumbnails. If there's a video it will often auto-generate the needed HTML to embed the video. I've also seen features where you link to a business's main website, but then are prompted to "like" their Facebook page.
How can I, as an independent website owner, have my pages reacts to Facebook in this way. For example, on the following page (link to a personal website) I have four images. However, if I drop that URL into a Facebook status update, there are no thumbnails for those images.
Also, while I've inferred several features of the notification box, I'm curious if there's other's I'm not aware of.
Again, while turnkey solutions and existing plugins are of interest, what I'm really after is what sort of meta data I need to embed in my own page, or what special responses I need to make to Facebook requests. In other words, how do I program a website to response correctly to Facebook.
Basically you convey that information to user in terms of open graph meta tags. From that Facebook picks up what type of site it is. Is it about a book or some music or some commerical brand or may be has a FB page linked to it? Check this documentation for general idea about graph objects - https://developers.facebook.com/docs/opengraph/using-objects/
Coming to specifically the image used as thumbnail, it is specified with og:image meta tag. Important thing to note about it is that FB caches that for ~24hours so don't sweat it if it doesn't show up. You can use this tool to check for your values which fetches it in realtime - https://developers.facebook.com/tools/debug
Also Facebook happens to have quite a lot of bugs around this, so it might take really long before it start showing up. If its picked up debug tool, then you are fine at code level. Not much that you can do about it.
I happen to know about this as I authored a tiny WordPress plugin for that and boy I know the support requests that used to come in. http://wordpress.org/extend/plugins/facebook-like-thumbnail/
Now for 3rd part of your question, even this is specified through meta tags only, like you have primary video content on your website, and you would like it to embed on Facebook when someone puts a link in the status box, so for that this link has code samples http://garethhooper.com/articles/social-media/45-integration/166-how-to-embed-your-own-videos-on-facebook-using-the-facebook-like-and-share-buttons.html
Hope that sets you on track giving you a head start :)
My organization is launching some local programs that they want to build up using social media. We already have some Facebook integration (likes, comments, etc.), but they would like people to be able to upload photos of themselves participating in these events. I was unable to figure out how to do this via Facebook, and we don’t have the time or resources to do this as a full-blown web app on our site.
Is anyone able to point me to a resource on doing this with
Facebook--something that makes more sense than the jumble of info on
their developer site?
Anyone aware of a photo sharing site that has an “anonymous
upload” or similar feature? Some form of moderation tools would
also be necessary (for obvious reasons).
Any other easy-to-implement photo sharing plugin that would not
require users to sign up for a custom service? (Facebook would be
OK since we’re already using that.)
I've tried searching for this many different ways on Google, but pretty much everything comes up for accessing one's own photos, not uploading to a separate group's. I've looked thru quite a few photo sharing sites too (flickr, photobucket, fotki, etc) but again, mostly they cover uploading only your own photos.
Thanks.
I'd like to offer my users the capability of either uploading a photo, or choosing one of their photos on Facebook (not only their profile photo).
Pulling the photo source from the Graph API isn't hard... However, does Facebook authorize us to use their photo link source in our apps, or must we download the photo, store it on our servers, and source them from there?
The safest bet is certainly to download the photo and save it yourself; as with web links I wouldn't trust that a photo link will be valid later.
That said, you then have to deal with deleted/removed photos and cleaning them up in your application.
I'm not a lawyer but it seems pretty clear either method is fine according to their developer policy. Specifically 2.2 states:
You may cache data you receive through use of the Facebook API in
order to improve your application’s user experience, but you should
try to keep the data up to date. This permission does not give you any
rights to such data.
My only concern would be the privacy settings on the photos and whether people would be able to access it via Facebook's url. But if you test it and it works and if the user explicitly selects the photo themselves, that would seem to be fine and wouldn't be much difference then them re-uploading it to your site.
I want to develop an online application and I am considering EITHER building a website with community features built in or building ONLY a facebook app. I was wondering if other people have had to make the same decision and what things I will need to consider.
The website I want to build will be an educational portal where people can make and take tests online
I disagree with some of the other answers here. There is a huge difference between a) trying to advertise a new place on the web and b) trying to advertise a new functionality of an existing place. Even if this new website would offer a very tight integration with Facebook and some other social platforms. Keep in mind: facebook users really don't like to leave facebook, no matter what the reason would be. That's why the click-through rate for the advertisements is so embarrassingly poor: http://en.wikipedia.org/wiki/Facebook#Company
That said you can of course always do both: build a website and offer the same functionality through a facebook app. However my opinion here is that if you're application only offers its users a single functionality, you'll be better off just doing the latter.
What exactly is the advantage you expect by creating a Facebook-ONLY-App for that?
If it's only about taking tests you can still build a "normal" portal and include some of the Facebook-functionality through the JavaScript-SDK, like posting to the wall, Single-Sign-On, find your friends and so on. This way the user still has the choice if he wants to connect with Facebook or not. This way you also don't minimize your userbase to Facebook-users
(yeah I know, "everyone" has Facebook these days... ;) Still not everyone wants it to be connected to every single site he's using through Facebook)
Considering this comment:
Well I guess its easier for people to recommend my app if it is a facebook app, is the main reason I want to know if facebook is a good option – Zubair Mar 3 at 14:51
Build a website and then add the Facebook 'like' button. See: http://developers.facebook.com/docs/guides/web/#plugins
You should put a Twitter button as well:
http://twitter.com/about/resources/tweetbutton
In my opinion you have to develop both. First develop you website. Although facebook is having millions of users But in my opinion you cannot implement every thing as freely as you can in your web application than facebook application. You should have a website and a page on facebook. You can integrate other facebook social plugins on your website to interact with facebook.
From monitization point of it is easy for new users on website than application on facebook. Other reason website especially related to educational purposes have a huge click through rate which you cannot find on facebook application advertiser.
What is the goal of the website?
If its to make money dont do a facebook app, you have far more control of your site by designing it entirely yourself.
If you want social networking features there are plenty of APIs you can tie in to which will provide you with functionality and allow you to link into facebook / twitter etc.
A website would look more professional, it would allow you to gather statistics on unique hits, revisits etc, having your own database of users means you can gather information and market your site more specifically ( which users took which tests).
A website also allows you to monetize it by adding advertisement if that is your goal, and you can gain search engine rankings.
If you want to get publicity for your website you can use facebook by creating a group / page for the site and promoting it that way.
Also your own website wont leave you vulnerable to changes in Facebook, what if you put in all this work and in a year the terms change and a portion of your app is now in violation of the terms. What if you want to add X feature and facebook wont allow it?
Basically your site = 100% in your controll, thats a big advantage to you. With facebook you loose that advantage but maybe gain a little in being able to use more of their features. Personally id always go for my own site.
You should go for the website first, then add the social elements in the website.
Like you can enable users to login using there facebook credentials. Like/share Button.
And later on, you can also go for the facebook app, when you want to shoot for much much more traffic. Therefore, whenever you think that you have figured out what exactly you want out of your application then only go for it, otherwise try your options with website. Because once your facebook app is up, you will get hell lot of traffic.
Let me know if you need help in creating facebook application or social elements enabled website. I have built an Facebook Easy API on top of all facebook features, which will enable you to easily access anything on facebook and meanwhile reducing your work effort.
You first build it like web app and use Graph API and FBConnect to use Facebook functionalities. Then you need to create a facebook app version also because getting facebook traffic is also required. People from facebook most like come to facebook app then to another web.
You will not need to convert it to facebook app, it will be just less in width and it would be a facebook iframe app. as I some where read that facebook is depreciating fbml and iframe app is recommended.
So now you can make both things, as I think , test app can have flexible layout so that you don't need to change width for facebook iframe. So you can both things by doing one.
thanks
i'm pretty sure many people will not agre with me, but IMHO you should focus on build a good Web-App that work well also on Mobile-Phones. keep it simple, intuitive, responsive, lightweight, cross-browser and straight to the point.
if your only concern is about "recommend your app to other people" make it SEO and Multi-Language too. google will do the rest.
then if you want make your app bold, slowly and planty of useless stuffs start to add all the facebook widget you want.
PS: i'm also on facebook, twitter,
flickr, google etc etc, i'm also
sharing photos, links and usefull
stuffs, my google rss reader is full
of links with tons of nice things, well i
have never had a minute to look at it, when i need something i just start searching google
I agree with most of the answers here—a native website is the way to go. Personally, I don't trust/like FB apps. Dunno what they do, and given the number of scammers out there and FB's lack of responsibility (IMO), I rarely if ever use an FB app.
Creating the website gives users choice about whether they want to share results/integrate with their FB wall/profile. Users don't like to be forced into something.
And in the spirit of adventure that is typical of SO, it's always more fun to build your own website than to build a template-based (sort of), boring and nearly irrelevant (drowning in a sea of other poorly made apps) FB app. But that's just my 2¢
In your case, I would do a hybrid. First, build your website, but integrate it with Facebook via connect. This way you can concentrate on building your value added services and let Facebook worry about the community.
I would also not ignore the Facebook app. Now, with iframes being fully supported on Facebook, you can adapt your existing site to work within Facebook with minimal effort, as long as you keep this requirement in mind when building your original application.