a chance of finding the bugs the users will uncover.
If we're watching users closely, and responding to what we observe and hear, our Web 2.0 applications could change at a high rate. Automated regression testing will be critical to allow that high rate of change while maintaining quality. Lightweight testing frameworks like Fit and Selenium may become more valuable to these testing situations.
Many of our users rely on our API to support their sites and tools. We'll have to keep our well-designed API stable by using something like the open-closed principle . We'll have to cover the API with automated regression testing to ensure it remains bug free.
A Web 2.0 application empowers its users, letting them tailor their own experience with the application. APIs expose the application to super-users who can take it even further. Simple, elegant, user experience-based design and equally simple and elegant technical design are critical. At the end of the day, building Web 2.0 applications will change the way you think about applications and the way you build them.
For more information on the open APIs mentioned: