We have an online pizza ordering system.
Now the client wants to integrate it in facebook.
The idea is everyone who is browsing facebook to be able to click on our App and order directly instead of going to our domain.
I can see that there are similar apps in the facebook search:
for example Flippin' Pizza Ordering : https://apps.facebook.com/flippinpizzafb/
Its exactly what we need.
The problem is that when I login the facebook dev platform.
When I click create a new app the only possible way to open our website in iframe (in facebook app) is if I choose it as Facebook web games.
Is this what I need or it's something different?
Haven't followed facebook dev stuff for a long time.. and every time when I log in there everything is changed..
I am working on PHP application which will be shipped to many users for their own.
App needs to integrate
Facebook api for auto post their web articles to their fb profile/page.
Twitter api for same purpose as above and to search for tweets/users.
Youtube api to upload videos to their user account.
I already have completed the software, Right now software has api settings menu for each of them. Where user create their own app on respective platform and setup app id/secrets etc... IT works fine...
But I am looking for a way where, we use our own app codes, and user only has to click on button which redirect them to their platform and they can allow access to our app. So they dont have to go through their own app creation.
Just like how login with social media things work...
I know thats possible and my question is not about how to do this...
My question is about IF I do that, will that create any App usage limitation issues for users ? For example, if I create my own Youtube app settings from http://console.developers.google.com/ and all users just authorise my app to their account, will it create any issues if all users (may be 2000 users) uploads upto 5 videos per day ? Will the usage limit counted per application or per user access assigned ?
I need the answer for facebook/twitter and youtube. I know some one how has already done this can answer this quickly and easily...
Thanks for reading my question...
I've been developing a desktop PC game in Unity which connects to Facebook in order to post messages about the player's progress (high score etc). The chosen method of how the app integrates with Facebook is currently set to "Website with Facebook Login". Everything is already set up and working (Open Graph stories, action and types) but after trying to submit the app for review, it appears desktop apps are not allowed to be configured this way.
The question I am asking is, if desktop apps are not allowed to use App Center, what are the preferred methods of posting messages to a users wall? There is the option of using normal feed posting but it is my understanding that this approach does not allow custom stories and will only display a generic message.
Does anyone have experience with the matter or perhaps has integrated it in their own game / app in the past?
Just to clear up a misconception in the question, an app can appear in Facebook's App Center even if it doesn't publish anything to Facebook - it must be on a supported platform (iOS, Android, or Facebook Canvas), though. And an app that doesn't appear in App Center can still publish to the site, too. The two are not connected.
That said: The feed dialog is actually highly customizable, and relatively easy to integrate into any game that can invoke a Web browser. Check out its documentation for details.
Additionally, you can create highly structured messages using the Open Graph. Doing this requires you to get the user's authorization, probably using a Web dialog. You need to request the publish_actions permission to do so; a few games (case study here, e.g.) have had remarkable success building out appealing OG implementations.
None of this is really specific to the Unity SDK at this point, I'm afraid, as it doesn't currently have native desktop support (just iOS, Android, and web player). But I hope it's helpful.
I'm interested in creating an app on an external website that will publish logged-in user's article reads to their timeline. However, I've noticed that when a story is published to timeline, other users who are not connected with your app, are forced to "Add to Timeline". To me, this defeats the purpose because I want users who are not associated with our brand to discover our content and then add it to the timeline if they are a fan of ours. Is there a way to turn off this setting? or is everyone FORCED to add an app to the timeline before they can see the content?
for instance, when I click on a story posted by the Washington Post on someone's timeline, I get this screen -> http://dl.dropbox.com/u/1169963/timeline.png when I expected it to just bring me straight to the article. Most users are going to abandon the app at this point and never click on a Washington Post article again
and it looks like people are making browser plugins to stop this from happening:
http://techcrunch.com/2011/12/01/frictionless-kills-facebook-social-article-readers-dead/
so, is there a way for developers to prevent this all together?
What do you mean about FORCED ? If i give permissions, after app produces timeline posts, it will combine and show as an application box in my timeline. But before it, i can see my friends timeline apps without installing them. Also same in newsticker in news feed...
For example in my profile http://facebook.com/chaylock , you should see my NIVEA Mega Kutu timeline app without interacting app..
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.