Web 2.0 from designer, developer and client perspective
Designer: Web 2.0 is when you have visually large elements (big icons, buttons, etc…), clear navigation, big fonts, cheerful colors and a lot of white space.
Developer: I think Web 2.0 is all about syndication. Having RSS feeds, XML-RPC calls, SOAP, API’s, track backs (link backs), socializing factor (user interactivity such as ratings, comments, etc…), tag clouds and of course extensive usage of AJAX.
Client: No doubt about it, Web 2.0 is when you have big fonts and buttons, warm and friendly colors, clear navigation and cool effects (AJAX) that produces rich end user experience, or so to say “wow factor”.
They are all right, more or less. I’d say I’m closest to developer’s point of view. Being both developer and designer and with intensive communication with clients, most of them don’t have a clue what “Web 2.0″ really stands for. All they know is that it’s cool and trendy term and that they want a “Web 2.0 look and feel”.
There are number of good articles on the net about Web 2.0 buzz, and what exactly Web 2.0 is, so I will not rumble about that but instead I will list couple of good resources for a reading and will cover a bit different aspect of it, Web 2.0 point of view.
Worth of mentioning list of Web 2.0 articles and resources:
- What Is Web 2.0 – O’Reilly
- Web 2.0 design style
- All Things Web 2.0
- Web 2.0 validator – This one’s actually very fun (or useful)
- Web 2.0 for Designers – Digital Web
- Web 2.0 – Wiki
- Web 2.0 Design Kit
- Web Development 2.0 – by Marc Hedlund from O’Reilly
“Architecture of participation” (Tim O’Reilly)
Definition of Web 2.0 from Wikipedia:
“Web 2.0, a phrase popularized by the first Web 2.0 conference in 2004, refers to a perceived second generation of web-based communities and hosted services — such as social-networking sites, wikis and folksonomies — which facilitate collaboration and sharing between users.”
| Question | Answer |
| Collective intelligence? | Designer: Wtf? … CIA ? Developer: Client: |
| Presentation and Layout? | Designer: Extremely important. CSS table-less design, W3C valid XHTML code, effective and clear navigation, clear content separation and a lot of “white space”. Developer: Client: |
| Socializing features? | Designer: It’s very useful to have it. I like designing UI’s and icons. Developer: Client: |
| Rich user experience and RIA? | Designer: Colorful and eye appealing design. RIA (Rich internet applications) is not my type of thing it’s more up to developers. Developer: Client: |
If you haven’t realized yet, answers were given with a healthy dose of sarcasm :), but are based on my almost decade long experience as a web designer, developer and entrepreneur.
Beta, Beta, Beta…Never get out of Beta
One question for which I still haven’t found an reasonable answer is “Why are all Web 2.0 applications always in BETA phase having “beta” stamp on their logo?”. Here is the list of possible answers to that question:
- They are constantly evolving with the help of “Collective intelligence”
- “Presentation and Layout” is tightly associated with the “Collective intelligence” and “Socializing features” so improvements are made on daily basis
- It’s a never ending story with “Rich user experience and RIA” so basically they will never leave the BETA phase
Maybe you have an answer, but I’d say it’s a trend…. again :).
Related posts:



Very helpful post, I just book marked it for any future reference to web2.0.
Chears.
March 7th, 2008 at 6:25 am