|
Success! Your email has been sent.
Bhopu / Tags /
Web 2.0 Technology
|
|
 |
Posted On
Dec 15, 2007
in
|
 |
|
 Most of us must have become aware of companies these days making an attempt to craft some very remarkable offerings in the social Networking Space. Majority of businesses believe that social networking will infuse their practices with everything around. You take my example; I must have signed for more than 20 social networks and member of different Web 2.0 community groups. In the last few months I have been keeping track of the apparently never-ending flow of news and blog coverage about Google's new OpenSocial model for social networking applications. A lot of specialists have remarked this Google’s move, as a shot to corner Facebook. To me this is a captivating set of developments to watch since Google's own growing social networking platform, Orkut, was overshadowed by Facebook in terms of overall traffic back in September.
Google’s OpenSocial
This OpenSocial by Google is an effort to introduce more influential, invasive social capabilities for the web, enabling developers to build applications for users to enjoy regardless of the websites, social networks or web applications they use. OpenSocial is said to be the first time multiple social networks under one common API, to further make development and distribution easier and more efficient for developers. This platform offers a single park of APIs for developers to learn for their applications to run on any OpenSocial-enabled website, helping to speed innovation and introduce more social features across the Internet. Sites which have already stanched support to OpenSocial include Bebo, MySpace, orkut, Engage.com, Friendster, hi5, LinkedIn, mixi, Oracle, Ning, Plaxo, Tianji, XING, imeem, Six Apart, Viadeo and Salesforce.com, representing around 200m users. Developers such as iLike, RockYou, Slide, Flixster, FotoFlexer, Theikos and VirtualTourist have already built applications using the OpenSocial APIs.
Why did Google introduce OpenSocial?
As the most trafficked website in the country and the most popular social network in the world, MySpace is one of the leading forces in the global social Web. Google realises that growing strategic relationship with MySpace and by joining forces can be an important initiative towards more success.
Google goal is to help shape the standards used between developers and social networks. Likely the move came from being shutout from Facebook. Not only did Google not get a piece of the social network, but Facebook uses a proprietary API that requires developers build apps specifically for it–sounds much like cell phone companies, doesn’t it?
As per reports from Techcrunch and NYT, initial social network partners signed on include Orkut, LinkedIn, Ning, Plaxo, Friendster, Saleforce, Hi5, Oracle. Application developers inlclude iLike, Flixterm Rock You, Slide. With Google's move to become the primary platform for social networking-based applications, however, Microsoft appears to have changed course. Late Thursday came news that MySpace would join Google's newly announced OpenSocial API platform, handing a huge win to the search giant. Bebo and others like Friendster are also joining Google.
Some essential things you should know about OpenSocial
As said by Don Hinchliffe here are few things you absolutely have to know about OpenSocial to have an outlook in relation to it:
OpenSocial only offers the lowest common denominator, not the full richness of each social networking platform
While application developers can create apps using the OpenSocial model and they will be able to run on dozens of different social networking sites, OpenSocial can't help you leverage the full capabilities of the site it runs on. Social networking site APIs aren't anywhere as complex as say, the Windows APIs, but we've seen this before with platforms such as Java, where the development model can't support the full capabilities of the underlying operating systems. Like Java, write once, test everywhere is the name of the game for OpenSocial and while economies in this model certainly exist, a single universal widget model tends to discourage product differentiation in favor of broad distribution. This means to get at the full richness of the underlying platform and create a competitive product, you have do custom coding for that site and you've just broken the reason to use a common application model.
OpenSocial is simple and straightforward but also capable of developing full-blown, rich Internet applications. 
And without server-side infrastructure. Developers can simply innovate with a few bits of markup and procedural code and drop it into the OpenSocial ecosystem and leverage the massive audiences and scalable infrastructure of OpenSocial compliant sites. OpenSocial even supports powerful interactive Web user interface models like Ajax explicitly. Like we saw last year, with the new productivity-oriented Web development platforms, this will change what's possible while also creating mountains and mountains of relatively useless, uninteresting apps amongst a few real gems. But a lot more wildflowers will bloom on the OpenSocial landscape and some will likely rise up and show us how useful these applications can be.
OpenSocial is from Google and excessive philanthropy should not be expected.
Google almost certainly thinks OpenSocial will ultimately be very good for Google, if not outright bad for a few others (probably Facebook). While the openness is encouraging, if OpenSocial is successful, Google has a plan to make that success work for it. Those plans may not always be to the benefit of everyone playing under the OpenSocial umbrella. User beware.
A new era in competency in social software is being ushered in by models like OpenSocial.
A lot more social applications are being created because of open social platforms have become so popular. But building successful social applications is a lot different prospect from building traditional business and consumer applications. Expect that many developers and software designers will fail to build applications successfully until we learn that a different focus and way of thinking is required. I've written before about the basic rules for building good social applications, but these are just the beginning. Understanding people is the key to building effective social networking applications, and that is often the hardest thing for us in an industry obsessed with connecting with each other via 1s and 0s.
My suggestions to Google
People don’t join social networks (Facebook or MySpace) to add apps to their profiles, and they’re not going to migrate elsewhere for the sake of a different API. No one is going to think, well, my friends are all on Facebook, but Orkut lets me help some third-rate startup monetize its assets by scattering random widgetjunk across my public profile… so it’s Orkut for me!
We have to agree no matter how "open" or "social," these apps will try to be, I just don’t see them being a selling point for prospective members. However, Google and Facebook should keep in mind that current members may really enjoy these options—and creating passionate users is just as important as converting new ones.
Google has fixed a meta-platform strategy, don't turn around -- Microsoft style -- and take advantage of their inside knowledge and control of the Open Social architecture to crush competitors.
Some Related Articles:
Essential Things about Google OpenSocial
Google OpenSocial Launch
Google launched Open API
Google to Out Open Facebook
Expectations from Google OpenSocial
Thanks Google for OpenSocial
Google Open Answer to Facebook
|
|
|
|
|
|
|
|
|
Posted On
Dec 05, 2007
in
|
|
|
 To a lot of people Web 2.0 might just suggest a new version of the World Wide Web, but to me it refers to changes in the way software developers and end-users use the web as a platform. It is nothing but a two-way communication between the users using the web as a platform. We can call it as exchange of information and network among the web users through some web based communities.
The main key characteristic of Web 2.0 is ‘Participation’, Participation, in this context, means the enrichment of a website by user generated content. In past websites use to serve a very basic information display mediums and the communication was just one sided. Options to edit, comment or add more to the existing content were almost non-existent. Web 2.0 has empowered the users to take part in the process of content generation.
Another very interesting feature in Web 2.0 is that it allows users to interact with like-minded users to exchange information or to discuss various issues using the web as a platform. That makes the whole process as much interesting as it can be while interacting verbally. Web 2.0 involves some emerging technologies, such as Web 2.0 AJAX, that allow developers and businesses to move, "beyond the page metaphor to deliver rich user experiences. And technologies like Web 2.0 APIs and RSS mean that users will no longer have their experiences dictated to them, but will instead have as much power to define their own experiences, as they are comfortable exercising it.
Designer should identify with the term Web 2.0
Having surrounded by web designers almost the entire day and I think it make a lot easier for them to differentiate the Web 2.0 sites. And the reason for this is that they try and describe that users perspective and their experience.
Web 2.0 crossing points as cutting edge 
We all are aware that RSS aggregators, search engines, portals, APIs and Web services, Google Maps offers the same functions as some other competitive services and tools on web. One of my favorites are the Flickr’s interface that is liked by all, Amazon also offers makes an attempt reaching further than its own site. All these new interfaces on web are changing the way we access and share information.
Are you submitting best Web Service for your users
Provide the best content to your users. Don’t just give them services but make them come back for more. One of the best examples for this are Amazon.com and eBay. The amount of commercial data that they provide to their developers is commendable and the best part is it is accessible to any developer who wants it.
Your Web 2.0 website should feature the following techniques:
- Rich Internet application techniques (Ajax, Adobe Flash, etc.).
- CSS
- Semantically valid HTML/XHTML markup.
- Syndication and aggregation of data in RSS/Atom.
- Clean and meaningful URLs.
- Extensive use of folksonomies (in the form of tags or Tagclouds, for example)
- Use of WIKI either totally or in part.
- Use of Open source software
- XACML over SOAP for access control between organizations and domains.
- Blog publishing.
- Mashups.
- REST or XML Web service APIs.
- Use of user-friendly content management systems (CMS) that are often open source, providing extensive website functionality at very low cost and reducing learning curves.
- Optimized search engine capability for balanced and largely used keywords.
Summary
Of course, designers are progressing the use of these Web 2.0 tools in many enterprises. But it remains to be seen whether these designers can sufficiently rein them in to serve their most strategic user objectives. And can these disparate technologies work in concert to achieve broader corporate goals?
Even with this simple design, the layout and Visual Studio is usually different. When you are developing Web sites this is probably okay, but when designing a Web site it is not acceptable.
This is where an expression Web 2.0 designer steps in. The focus of Web 2.0 Designer should be to provide their users with a clean, clear and complete view of how their Web page would look like. I feel that every company can make a smart move by creating these various Web 2.0 tools. Not everyone is a designer and not everyone is a developer. Sharing tools in one big huge product can be overwhelming. As it is, if the designers and developers working together and adapt the new Web 2.0 trends they can create the best Web 2.0 user experience.
Some Related Articles:
Web 2.0 for designers
What is Web 2.0?
Delivering Rich Web 2.0 Experiences
Better E-learning for designers
Rich Web 2.0 Applications
Web 2.0 Design Centre
Web 2.0 Ajax pioneer emphasizes user experience
|
|
|
|
|
|