1 / 40

New trends in web technologies and -business

New trends in web technologies and -business. Tommi Tuikka 18.3.2008. WWW evolution. 1989: First proposal, Tim Berners-Lee 1993: Publicity begins, Mosaic browser 1994-1997: Web 1.0, Static web pages 1998-2001: First rise of web business, DotCom bubble

norah
Download Presentation

New trends in web technologies and -business

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. New trends in web technologies and -business Tommi Tuikka 18.3.2008

  2. WWW evolution • 1989: First proposal, Tim Berners-Lee • 1993: Publicity begins, Mosaic browser • 1994-1997: Web 1.0, Static web pages • 1998-2001: First rise of web business, DotCom bubble • 2002-2003: Recovery from DotCom bubble • 2004-2007: Web 2.0, Second rise of web business

  3. WWW evolution Faster internet connections New business needs This was called Web2.0 (O’Reilly 2005) Web as software platform New user interfaces Social Web

  4. User and WWW evolution • User as passive receiver, reader: Traditional web pages • User as active participator, writer: Forums, guestbooks etc. • User as developer: Facebook, Google maps etc.

  5. The layers of Web 2.0 Social layer: More users, better application Technical layer: Ajax, RIA:s, SOA etc. Architechtural layer: The Web as platform

  6. Web 2.0meme-map(O’Reilly 2005) PageRank, eBay, Amazon:User as contributor Blogs:Participation, not only publishing Web 2.0 BitTorrent:Radical decentralization Flikcr, del.icio.us: Folksonomy not taxonomy Google AdSense:Customer self-service enabling the long tail Gmail, Google maps and Ajax: Rich user experiences Wikipedia:Radical Trust Strategic Positioning: • The Web as platform User Positioning: • You control your own data Trust your users An attitude, not a technology Core Competencies: • Services, not packaged software • Architecture of participation • Cost-effective scalability • Remixable data sources • Device-independent Software • Collective intelligence Web consists of components The Long Tail - principle Data is ”Intel Inside” Rich user experiences Software that gets better the more people use it Continuous beta -version Playing and entertainment Hackability of services Granular Addressability of content User behavior not predetermined The right to remix – Some rights reserved

  7. Web 2.0 main features • Web as platform • End of versioning, continuous beta-version • Lightweight programming (JavaScript, Web-APIs) • Rich user interfaces, usability • Harnessing of collective intelligence • Open communication and decision-making • Free delivery and reuse of data

  8. Web Technologies Web Technologies

  9. Web as platform: Ajax and RIAs Ajax Web as software platform XForms Java applets RIAs Web software needs new UI:s!

  10. Ajax No Ajax Ajax Client Server Client Server Login Login User Data model User Data model Response Web page Application- logic Client App moves Application logic User Data model Request Response Web page Continous data exchange Request Client application User Session User session Response Web page Request Logout Logout Exit Database Exit Database

  11. Ajax Frameworks • Prototype (JS library) • Scriptaculous (JS library) • Zend Framework, Symfony (PHP) • JSF, Spring-DWR (Java) • ASP.NET Ajax Toolkit (.NET) • and many more…

  12. Rich Internet Applications (RIAs) Desktop applications Web applications Platform indpendent applications Low delivery and maintenance costs Universal availibility of applications Fast and cost-effective development Richer user interfaces Asynchronous page loading Interactivity and fast user response More complex applications possible RIA

  13. RIA technologies • XHTML and Ajax • Adobe Flex • Open Laszlo • Microsoft Silverlight • JavaFX • and many more…

  14. RIA comparison1

  15. RIA comparison2

  16. Adobe Flex architechture Browser Flash Player XML-data SOAP, REST, etc or RMI Flex-application Binary SWF-data Web server Application server: Java appserver, LAMP or ASP.NET Web Services Databases Media files

  17. Web as platform: Web APIs and Mashups Java RMI Web APIs Web as software platform Web Services RSS Mashups Web software needs new data-exchange interfaces!

  18. When to use or not to use Ajax or RIAs? • When customer needs it • When we are moving desktop apps to Web • When UI is complex • Traditional Web apps not necessarily need Ajax or RIAS. UI drawbacks possible. • Apps with critical importance (eg. society services) can not depend on Flash or DHTML -support

  19. Service Oriented Architechture (SOA) SOA 3-TIER ARCHITECHTURE ESB Homogenous Language dependent Centralized application tiers Code-centric applications Request/Reply -driven HTML -pages Heterogenous Language independent Massively distributed services Flexible composite applications Request/Reply, Events, Sub/Pub Ajax and RIAs

  20. Traditional Web Service User request Web Service -Server Web-application Web Service:Method, class, component etc. SOAPclient SOAPserver Web Service-registry (UDDI) optional SOAPserver WSDL

  21. Classifying of Web APIs • REST Web APIs – XML, JSON or text over HTTP • SOAP Web APIs – SOAP over HTTP • RSS Web APIs – RSS over HTTP • JavaScript Web APIs – JavaScript method calls • and some more…

  22. Comparison of general Web APIs

  23. Web APIs and software development Applications on Windows or Unix -platform Applications on Google or Yahoo -platform Before Now www.programmableweb.com

  24. Mashups • Mashup = Web application hybrid • Needs Web APIs • Data mashup of two applications gives additional value compared to separate applications • Google maps based applications are most typical • Data security problems are possible

  25. Mashup types WWW - global SOA Web Services Company Intranet REST Web Services JSON SOAP RSS SOAP JMS Proxy http(s) HTML-page Integration Code JavaScript1 Server JavaScript2 JavaScript3 JavaScript WWW-browser WWW-Browser Client-side Mashup Server-side Mashup

  26. Creating Mashups • Code yourself • Code yourself with application frameworks. Some of them support creating mashups. • Mashup software: OpenKapow, WaveMaker Google mashup editor

  27. Open Source and Web development tools • Web development tools will evolve only if they have adequate number of users and developers • Open Source products have more developers (and often also users) than commercial products • In the future all important Web development tools will be OS (If they are not, they are not so important anymore…)

  28. Web Business Web Business

  29. Change of Web business Transaction Collaboration Discussion Feedback Customer Contribution Customer network Organization Organization Web 1.0 Web 1.0 Web 2.0

  30. Web 2.0 Business models Technology based mostly free services Technological innovation Unique service which is useful for user Basic service is free Additional properties are chargeable Very much users -> enough paying customers Skype, Habbo Hotel etc.

  31. Web 2.0 Business models Network-based free services Appilication has very much users and interaction between the users Users create content and attract more users Service is free Cash flow is created mainly by advertisements Ads are directed to people with specific interests Youtube, MySpace etc.

  32. Web 2.0 Business models Completely fee-based services The service must be very valuable for user Users pay subscription fee or a little fee every month Advanced technology and expert users make the service valuable Typically entertainment or expert services World of Warcraft, Zune etc.

  33. Enterprise Web 2.0 The service is inside company intranet Social network of restricted group Can help decision making and harnessing collective intelligence or ”silent knowledge” User can develop situational applications: easy made data mashups of actual enterprise data Lotus Notes, WaveMaker, QEDWiki etc.

  34. eServices and Web2.0 • Public sector services are going to the Web • Paper application forms -> electronical forms • Future application forms are intelligent, they can help users filling them • Handling of forms is automatic, no staff needed • XForms, Adobe Live Cycle Designer

  35. The Long Tail Less popular or less common products create ”The Long Tail”. Before it was not possible to sell them. Nowadays it is possible to sell them by social web networks: NetFlix, eBay etc. Availability of products from shops Number of products

  36. Web 2.0 Business: Major transactions • YouTube was sold to Google for 1.3 billion dollars • MySpaces advertising rights were sold to Google for approximately one billion dollars • MySpace was sold to Fox Interactive for 400 million euros • Friends Reunited was sold to ITV for 240 million euros • Xfire was sold to Viacom for 80 million euros

  37. Web 2.0 examples from Finland 1 Finnish innovations • Habbo.com • Mikseri.net • Vapaa-aikavirasto.com • Mywot.com

  38. Web 2.0 examples from Finland 2 Clone applications • Sporttube.fi (Youtube) • Telkku.com • Sentti.fi (Bidster) • Koulukaverit.com (Classmates)

  39. The Future? The Future?

  40. The Future? • Web 2.0 -development continues • Rise of eServices • Better utilization of Mobile Web • Semantic Web applications: developers add semantics to data • New user interfaces: audio, neural impulses

More Related