Having done many fb apps and making heavy use of twitter bootstrap by myself for other projects recently (oh god, app development on lightspeed!) i first looked at it thrilled: hey cool- this will come in handy! But after about 5 seconds: wtf?
This is just twitterbootstrap painted blue.
Using this for your facebook apps would NOT give them a genuine facebook look but make them only look cheap.
The typo is not right. Font sizes, line spacing - everything. Forget about the columns. They are twitterstyle, not facebook. Buttons? They are grey and blue, yes - but not facebook style. Tables? Not at all. I could continue this list for every single element! Facebook has unique tabs, unique breadcumbs. Completely missing!
My quick advice for getting a nearly facebook-like style in your appe in seconds: embed their CSS in your header. When you investigate a bit how they build their page elements, you can mimic their style really quick.
And for the "fb bootstrap": nice idea. Awful implementation. Stay away from it. But everyone has to decide for himself - seems like most people like it, tough.
Why does this happen (appearently) more on PHP than other languages? (please correct me if I'm statistically wrong)
The reason why I created my facebook framework: there simply is no other.
First off, it's close enough. Close enough is more than enough for something like this as Facebook has rules about looking too much like the rest of the site. Having it be close but not quite Facebook-style is great for plausible deniability if they ever gave you a problem and you were inclined to try to defend yourself (it may be a losing battle but at least you have the option).
The author makes it clear that it's based on Twitter's bootstrap so it's not surprising to see it just "painted blue" as you say. Honestly, I looked at this and saw that it was more than enough to get you started.
Whenever you create a boilerplate, especially one that you release to the public, you walk a fine line between offering a solid, customizable foundation and giving people far too much structure that they have to undo. Every single framework I've ever seen (even the one I made for myself) has been criticized for being pretty much a completed project sans content. It's almost a losing battle. Give people too much and they complain it's no longer a boilerplate. Give them too little and they say there's not enough for it to be useful. I think this project walks that line quite nicely.
So I guess what I'm saying is give the guy a break. This is cool and useful. It doesn't look cheap either. I think you went too far with that statement. It isn't totally Facebook style but close enough goes a long way. I absolutely am not trying to be antagonistic. Everyome has the right to criticize especially since this got posted here on HN. I don't want to say you can't criticize but just be fair about it. It isn't as bad as you make it out to be. To me it's not bad at all. Though it may be bad to you, which is okay, don't you think there's at least some good things about it? I don't know, I have this weird paternal instinct that kicks in whenever I see criticism I think is too harsh.
It seems like the guy is still working on it - so maybe it just became popular too quickly before its ready.
On a second look, the dialogs look much better now.
And as I sayed in my original post: everyone has to decide for himself ;)
If facebook ever thinks you have done wrong, there will be no chance for "plausible deniability" because they simply delete your content and will never contact you or answer your mails. So why don't be perfect in the first place?
The small-but-significant differences between this framework and Facebook (e.g. button styling!) will make any app built using this look decidedly sketchy.
Every other "platform" provides UI guidelines with libraries/frameworks to allow others build products native to their platform. Facebook have made no good attempt at this, which is why this is a great project!
Currently, if my user navigates a few pages deep in my app and clicks the back button, it exits the app and goes back to Facebook. Quite annoying... Thanks!
If you do that though, there are a few other issues - you may have to account for pages that do/don't have the Facebook signed_request post data - i.e. you probably need to store it in a session or cookie (and deal with the relevant IE7 cookie + iFrame issues by settings P3P header if you support IE7. Can't remember offhand if it is a problem in IE8.)
Obviously more complex apps where navigation is handled through AJAX get tricky when you can't access the container frame. Maybe look into history.js (https://github.com/balupton/History.js/) and see if it works in a Facebook app?
I decided not to support IE7 since this is a brand new app. It will be IE8+. I had to deal with the P3P issue in the past and it was a pain. Hopefully IE8 isn't as picky.
Thanks for the help! I now have something to investigate.
Your other option is to have a back button in your iframe in a prominent location and hope your user uses that instead of the browser back button.
If you somehow figure out a way to make pushState work, you should probably still have a back button in your app, for old browsers. Or at least display it for only old browsers.
So a link in my iframe app would be something like this:
<a href="https://apps.facebook.com/defensio/archives/index target="_top">Deleted</a>
This will create an iframe with https://facebook.defensio.net/archives/index
I'm not sure if this bootstrap is already compatible with Twitter's (i.e. as simple as changing CSS file), haven't tried this bootstrap thing, but it would be great if it is!
"App does not use Facebook trademarks or express or imply any affiliation with or endorsement by Facebook"
This is a rather vague statement that I could easily see being used as the justification for squashing someone's app. This is why I've always made sure any FB app I make doesn't completely rip-off Facebook styling but contains enough of my own styling to not appear to be part of Facebook.
Given that Facebook apps are completely dominated by large companies these days, I'm puzzled by how useful this would be.
Are people really still building FB applications?
I thought the only real action these days was in the mobile space.
> Fbootstrapp is a toolkit designed to kickstart development of facebook iframe apps