Web evolution and Web 2.0

• Carles Mateu is associated with Web Applications, and is from the Department of Computer Science and Artificial Intelligence at the University of Lleida, with the website http://carlesm.com.

Web Evolution

• Web 1.0 is read-only (R/O).
• Web 2.0 is read/write (R/W).
• The philosophical shift from "me talking about me" to "all talking about everyone."
• Technology allows reuse/share/remix/rewrite of everything, everywhere.
• There's a social shift from reader-consumers to creators/producers.

Web 2.0 characteristics

• Focus on simplicity, usability, and user experience
• Folksonomy, use of wikis, and social software
• Encourages participation in ways such as blogs, audio and video
• Facilitates a shift toward convergence, data remixing
• Emphasis on APIs, guiding by data
• Promotes standardization, separation of form and content using CSS
• Supports standards web microformats

Web 2.0 Key Aspects

• Conversations between companies/organizations and consumers become more transparent.
• Business models are lighter, with smaller and focused teams.
• Reputation and trust are vital due to user-generated content.
• User mobility is crucial, allowing access from any device or location.
• Re-mixing information leads to new, derivative content.
• Sharing information in various formats is emphasized.
• Communication prioritizes simplicity and ease of use.
• Folksonomies are used for decentralized tagging of information.
• Social software meets the communication needs of individuals.
• Social networks facilitate relationships and common interests.

Web Design Principles

• Using multiple technologies such as ATOM, JSON, AJAX, CSS, XML, and JavaScript.
• Separating data and presentation layers.
• Using server-side and client-side scripting.
• Leveraging existing APIs for easier data access and isolation from design changes.
• Reducing page load time by getting only needed data
• Being mindful of scripting impacts and connection speeds.
• Improving search engine visibility by ensuring proper indexing of text, content, and dynamic pages.
• Applying Object-Oriented Programming (OOP) techniques.
• Using existing standards.

API Mashups examples

• Google Maps: Mapping services, 1468 mashups.
• Flickr: Photo sharing service, 350 mashups.
• YouTube: Video sharing and search, 271 mashups.
• Amazon eCommerce: Online retailer, 248 mashups.
• Microsoft Virtual Earth: Mapping services, 151 mashups.
• eBay: Online auction marketplace, 141 mashups.
• 411Sync: SMS, WAP, and email messaging, 120 mashups.
• Yahoo Maps: Mapping services, 116 mashups.
• del.icio.us: Social bookmarking, 111 mashups.
• Google Search: Search services, 111 mashups.
• Yahoo Search: Search services, 108 mashups.
• Yahoo Geocoding: Geocoding services, 76 mashups.
• Twitter: Community site, 68 mashups.
• Google Homepage: Portal gadgets, 62 mashups.
• Last.fm: Music playlist management, 60 mashups.

12 Factor App Principles

• One codebase tracked in revision control with multiple deploys.
• Explicitly declare and isolate dependencies.
• Store configuration in the environment.
• Treat backing services as attached resources.
• Strictly separate build and run stages.
• Execute the app as one or more stateless processes.
• Export services via port binding.
• Scale out via the process model.
• Maximize robustness with fast startup and graceful shutdown.
• Maintain parity between development, staging, and production environments.
• Treat logs as event streams.
• Run admin/management tasks as one-off processes.