My friend at Good Web Work asked the question,”To what problem is Google+ a solution?”. I started to write a comment on his post, but after the scroll bar popped up on the comment form realized this was blog post material .
I have no idea what I’m talking about
I haven’t used Google+ yet so take this opinion as one from an outsider looking in. I have watched videos, played with demos and read reviews. My first impression: The design looks nice; a clean minimalist interface with an ample use of white space. The overall impression I get is an easy to navigate, light and responsive website. Three cheers for Google for finally letting their designers do their jobs.
You gotta problem?
What problem does Google+ solve? Well, that depends on your definition of a problem. Did the world think Myspace was a big problem before Facebook came out. Probably not, since most users had not experienced anything better. After Myspace users got a taste of simplicity from Facebook’s early interface, the contrast was almost offensive. Now Google+ seems to be positioning themselves as the cleaner, friendlier interface of the social networks.
Competing for the best user experience
I can come up with a few problems Google+ at least attempts to solve. What about the problems of inferior user experience and lack of healthy competition?
The Problems Google+ May Help Solve:
Inferior User Experience – Facebook is great, but there’s plenty of room for enhancements. Google+ Circles, Huddles, and Hangouts appear to be new take on common social media functionality. Circles are supposedly a big improvement on Facebook “Lists”. Allowing you to group friends more easily and filter what you see and what others see gives more control to the user and hopefully improves the user’s experience. You also have the ability to “Follow”, in the Twitter sense, someone you aren’t “Friends” with, in the Facebook sense. The best of the both worlds perhaps.
Lack of Healthy Competition – Facebook has exploded in the last several years with no one coming close to competing with them as a full social platform. Google can and will compete for users. This will cause Facebook to improve their service in response, only giving users more options and better social media experiences.
For most people the current Facebook interface is familiar, so they wouldn’t consider it a problem. The mere fact that Google is launching a very serious social media platform designed from the ground up with the user in mind will benefit all users of social media even if they aren’t using Google+. They are raising the bar and their competitors will have to jump higher.
Yes, according to Neil Postman‘s definition of a problem, a newer/better social network from Google may not solve any of the world’s biggest problems.
* Image taken from the cover art of the world-famous Tetris video game.
The first time I heard about Object Oriented CSS was from a tutorial on NetTuts. At the time, I viewed OOCSS as just another random framework somebody was imposing on the web community. I had not given it much thought since then, until I listened to Nicole Sullivan‘s interview on The Big Web Show. She’s a CSS pro who started OOCSS.org and the open-source OOCSS project on github. Nicole has been hired by mega-sites like Facebook to optimize their CSS files. FACEBOOK! That must have been insane!
Oh, OOOOOOOOOh CSS!
Having spent a chunk of the last 4 years of my life learning and working with CSS on a daily basis, I was intrigued to hear the thoughts of an elite CSS Ninja. Half way through the interview I found myself inspired to become an Object Oriented CSS-er.
I started browsing the Google tubes and found a nifty presentation created by Nicole. Enjoy:
If you didn’t have time to click through the slideshow here is a super tiny break down:
Two main principles
Separate structure and skin
Separate container and content
Applying these principles creates efficient CSS code. This means cleaner smaller CSS files that load faster.
What does it look like?
Well, kinda like this…
This basic structure is very flexible. By adding classes you can “extend” the object class to fit each scenario the design requires. For example:
[html]<div class="object simple half"> …[/html]
Extending the object class is faster to write and to load.
I’m extremely guilty of writing overly specific CSS, thinking that everything has to have its own ID. Trying to be too semantic, I guess. I’ve confused myself by listening to too many different theories about how to structure your HTML and how to reference selectors in your CSS files.
I’m realizing that all I’ve needed was a little objectivity.
My latest free desktop wallpaper design is an arrangement of dark gray blocks on a black background similar in layout to Piet Mondrian‘s Composition II in Red, Blue, and Yellow, that he painted in 1930. I’m not saying its as revolutionary as his painting, only that it shares the same balance of visual weight. If you like this wallpaper you can download it for free. Love it or hate, feel free to express your opinion in the comments.