I think my 'timeline' should be representative of photos I've uploaded, posts I've made that I want to highlight and events I went to. My 'wall' should be a straight-forward top-to-bottom feed of stuff I've posted and stuff people are sharing with me.
I hate the timeline, as I can't track two columns, and probably wouldn't like a grid also for the same reason.
I logged in to Facebook a minute a go just out of curiousity, and struggle to actually find my homepage, first I get badgered by Facebook, I then accidentally stumble upon my Timeline (which I hate), I then click the Facebook logo to go to a homepage, which happens to be a feed - or rather what I deem my own homepage. Confused! And it happens every time.
I really only ever want that to be on most recent.
My other problem with Facebook interface is that I just don't know where to go to "do stuff" - eg: if I want to unlike a company page. There's a bunch of little icons in the top blue bar (10 clickable things in that bar), and then there is the list down the LHS, and the almost hidden follow / report this post button.
I do like the fact that it's being refined; I notice the occasional difference. And the new privacy announcements were clear enough.
I guess I don't use FB like most people use FB. I only have less than 50 friends and I don't like a bunch of products or companies.
As an archive it's great, you can exactly see what someone liked/posted in previous months, but it's not a feed, and that's what I would like someone's profile to be, a feed of his activity.
Came here to say this. "Eye candy" != easy to use.
Of course not. That's a highly efficient way to represent visual icons. Facebook has a much different focus: for one, it's a linear idea (in its current formulation), either by date or by how facebook decides to prioritize your stuff (grumble).
That said, I would probably much prefer to eschew all icons on android for a nice text list.
The assumption is that because both designs share a common attribute they are both intended for the same purpose and therefore if one design is bad for a particular reason, the other design must also be bad for the exact same reason.
This isn't necessarily true with Pinterest, which has a different purpose to Facebook, and therefore likely requires a different UI.
I .. I'm not sure if you're serious, but that is either smart, insulting or both. It's true that cleavage and nice smiles were there, but noting it as a non-production look, - that's a bit bleak.
The design looks great. I can't wait to hear my friends opinions as I don't use Facebook on regular basis.
likewise, if Facebook chooses to saturate their pages with images they know are generally poorly shot, you are allowed to question Facebook's ability to dress itself.
a. Facebook does not get to choose what photos get uploaded
b. Facebook knows the overwhelming majority of these photos are of poor quality
as such, it would be short sighted for Facebook to incorporate a design which relied so heavily on shitty user generated photos.
The point is, the new layout discussed here relies in some way on the pictures being not shitty. The discussion here is about a layout for content that is not under Facebook's control.
every photo on Facebook is user generated. an overwhelming majority of them are bad photos. Facebook is completely aware of this.
as such, it would be an irresponsible design choice for Facebook to create such a huge presence for those photos, like the design proposal does. likewise, it is irresponsible of the proposal author to only use high resolution stock photos of decent looking people for their design.
perhaps my original post was not crystal clear. in retrospect i maintain that it was a fine explanation, albeit terse- and out of context given my misinterpretation. regardless of my post's clarity, your response makes you sound like a dick.
I respectfully submit that had what you meant to say been so clear, or had you followed your own advice to "read both posts carefully", perhaps you wouldn't have made the mistake twice.
Of course if you're making a website for models or photographers, then ignore that completely. The take-away here is to know your audience, and design accordingly. Facebook should be (and currently is) optimized for getting a quick pulse on what's happening in your social circles, and the designs presented here are a poor way to accomplish that.
[1] Long names cause weird word-wrapping and overflow issues in many designs. India seems to have a high density of (by my standards) unusually-long names, so if you expect to have a lot of Indian users that kind of thing is really important to consider.
Well, 50% of the people on Facebook don't have cleavage. The other 50% are doing duck faces instead of smiling. You can't design around some abstract ideal.
Here's an earlier (2006!) redesign by Information Architects (iA). I think this is a lot cleaner and solves the information overload problem better.
>> I also agree that it looks a lot nicer because of the high-end stock photos.
Exactly. This looks like a first-year design school project for these, and so many other reasons.
This design would fall apart without visually simple photography that tailor fits to the grid. The right way to approach a redesign would be to collect an aggregate of typical facebook photos, and use them as examples.
In terms of graphic design, it's a huge improvement, not so for usability/ux. The timeline is chaotic. Small type. Navigation/content areas undefined, too much layering.
Both funny to read and true as well!
I also agree that it looks a lot nicer because of the high-end stock photos.
Edit: scrolling down further, there are some other UI refreshes that I do think improve the experience overall - the calendar and photo album views stood out to me. But I think it's important to use ugly people with weird names in your designs to gauge how it will actually look in production! The dark theme on pages, for example, looks very clean with Apple and Adobe as featured, but I imagine will look pretty dreary to stare at all day.