Be the first to write a review
Web 2.0 best practices
If you visit this Web site regularly, you’ll realize that recently, we’ve looked at the topic of Web 2.0 in some detail. This approach to Web applications aims, among other things, to create a more responsive experience for users. Both Ajax-style and Flash/Flex rich internet applications are common approaches in the Web 20 world.
The Web 2.0 approach is relatively new to the Web world and in this article, I want to look at some of the emerging best practices for building Web 2.0 applications. Even though some of the component parts of approaches like Ajax have been around for a while, developers are still coming to terms with Web 2.0. As we get more and more experience building this type of application, more and more best practices emerge.
I’ve attempted to put together a list of best practices for building Web 2.0 applications. See if you agree with what I’ve written or if you’ve got any more to add. I’m going to cover the following:
- Minimizing server traffic
- Using appropriate interface elements
- Providing user messages appropriately
- Indicating changed or refreshed data
- Picking the right approach for applications
- Enabling SWF files
- Using frameworks, toolkits and script libraries
- Working with object-oriented design patterns
- Separating script into separate files
There aren’t any resources to download with this article. Rather, it discusses each of these best practices and provides a rationale behind why each is appropriate.
Sas Jacobs
Hello. I'm the Principal of Anything Is Possible, an Australian web development business specialising in web applications development and training. I'm interested in using Flash with dynamic content and I've presented at a number of International conferences on topics relating to applications development, XML and scripting components. I have recently released my second print book Beginning XML with DOM and Ajax to match the first one - Foundation XML for Flash. I have a business web site
and a personal web site.