3 ms·

This is good advice. There are at least two things at play here: a. Do we want some amount of branding to our app independent of Facebook? b. Does it make

• unalone 18y ago
  I can't answer b: my knowledge of coding for Facebook is very minimal. I've used tons of applications, though, mainly when writing for AF, and I think that the absolute best path to follow is to look at what Facebook does for its own applications. By far, they're the best ones out there, even if Facebook doesn't have to worry about branding. For a, though: the best applications are the ones that stick at the very least to Facebook's usual designs in regards both to colors and to line thicknesses: in other words, the applications that look native. The reason for this is that you're competing not with other calenders, but with Facebook's native applications. When I'm on Facebook, every app is a click away. And so you're competing with Facebook's apps, all of which are spectacular, and you're competing on their playing field, in which you have no control over the look of the site you're on. While you should definitely brand yourself, don't brand your design. Keep it looking like it belongs to be on Facebook, more or less, because any active difference will be seen as a negative. Furthermore, if you're on Facebook your app has to play by their rules: focus on interaction with friends above everything. If you want some instances of applications that I found incredibly good, check out Packrat - http://apps.facebook.com/packrat/ http://apps.facebook.com/packrat/ - or Projects, even if it broke a bit in the upgrade to the new Facebook - http://apps.facebook.com/divshare_projects http://apps.facebook.com/divshare_projects