Archive for April 2011
Obviously I was asked why I haven’t done all that withing the already existing FacebookBundle which is multi purpose of which a canvas app could be just one.
When you followed my posts for the last few weeks you might have noticed that I wasn’t exactly happy with my attempts to combine Symfony2, its security component, FacebookBundle and Facebook itself.
I just couldn’t get both working together the way I wanted them to. Partly because of Facebook and partly because my lack of understanding the Symfony2 security component and all its (yet to be completely documented) possibilities and its use in FacebookBundle. So I decided to invert my working process and start from plain PHP and authentication adn authorization with Facebook and then slowly progress towards Symfony2 integrating more and more with the security component.
Now I can present the first working bundle.
Today I wanted to share my latest development of authenticating with Facebook using Symfony2. But while it now finally works as expected it is not ready yet to be published.. so check back here tomorrow.
Meanwhile I want to share a link and infographic with you about online marketing that puts things in perspective and can help to understand the flow of requirements but also to get you in a position where you can be a good adviser to your client.
If you want to develop a Facebook application that runs within the Facebook frame you want to write a canvas app. The first thing you will want to do is to allow your user to authenticate and authorize your app.
Only that a pure server side solution simply doesn’t work..
When coding with Symfony2 and Doctrine 2.0 though I often get the feeling of not knowing what to do with this freedom and I already heard voices of fellow symfonians to wish a bit of that old magic and restriction of symfony 1 back. Bluntly put: if a framework doesn’t decide anything for you – where’s the benefit?
If you have a history of seeing a rant where none is indended you can stop reading here.
When you start a new online project you often start with an idea of a service that simply “should exist”. As a developer you might concentrate on the user experience and functionality but when you want to get going you will often need content of some sorts. Videos, texts, images.
But often you are not equipped to actually produce any content so you need to get it somewhere else and eventually you will be faced with copy rights.
If you develop for a Facebook application: think again!
Not only is their Graph API not too well documented and sometimes inconsistent (compare attaching a picture to a status message or an event) but the also restrict the use of it in some cases.
For a little app I needed a picture to add to an event, so I used the Graph API to search for an image, got one and used it. Using the same picture in a status message though doesn’t work..
To answer this I think one has to understand the effects a software – a framework in this particular post – can have on the business.
Many – including myself – will have done this by judging its technical parameters as well as throwing in some gut feeling.
But from a business perspective those parameters aren’t very meaningful. In the end the decision has to pay off in money.
What many of those developers seem to be unaware of is the possibility to bundle multiple Graph API requests into one single batch.
Unfortunately the official documentation uses raw
cURL and does not document how this can be done with the SDK.