Sometimes, the need arises to have a facebook app that will be reused across several pages. Those pages may or may not be related in some way, but the content or functionality of the app should carry across them. It MAY seem easier to just create a new copy of the app for each page, but that's going to be a nightmare to maintain if you're delivering anything more than a tiny chunk of content.
To get around this, you can create a single app that is called by as many pages as you want. This single app will leverage the "signed request" that facebook passes to all apps. There's a lot of useful data in the signed request, like whether or not the user has liked the page (I referenced this in an earlier post about reveal pages). For this example, I'm only interested in parsing the request and getting the page id, and then using this to determine what to display.
Wrapping up work on a site that does some interesting things:
facebook connect
facebook interactivity
parallax scrolling background
conditional css that targets chrome using php
I have no idea if I'm under an NDA for this client... I don't think i am, but for safety's sake, I just won't list it here for now.
I'm writing some code for a client that allows a user to sell their soul, and in return... give me their email address, their profile photo, and the ability to post messages to their wall. Exciting stuff!
I was asked to create a simple page on "Ye Olde Facebooke" to display two possible pieces of content, based on whether or not the user has "liked" the main page. Apparently, people refer to this as a "Reveal Page"...
I'm putting the code here for future reference. It was a delightful departure from the nightmare that was my last Facebook app. Hit the "read more" link below to see.