Postmodern Web Apps

  • 3,026 views
Uploaded on

 

More in: Technology
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
No Downloads

Views

Total Views
3,026
On Slideshare
0
From Embeds
0
Number of Embeds
2

Actions

Shares
Downloads
71
Comments
0
Likes
7

Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide

Transcript

  • 1. Building Post-Modern Web Applications
  • 2. Agenda
  • 3. Agenda No Agenda
  • 4. Me _ Working at SinnerSchrader _ Joose - JavaScript Meta Object System _ Bespin - Code in the Cloud _ http://joose-js.blogspot.com _ http://twitter.com/cramforce
  • 5. The term postmodern is described by Merriam- Webster as meaning either quot;of, relating to, or being an era after a modern onequot; The American Heritage Dictionary describes the meaning of the same term as quot;Of or relating to art, architecture, or literature that reacts against earlier modernist principles, as by reintroducing traditional or classical elements of style or by carrying modernist styles or practices to extremes.
  • 6. I won‘t talk about why but about HOW!
  • 7. A Brief History of the Web
  • 8. A Brief History of the Web In the beginning there was the page
  • 9. A Brief History of the Web In the beginning there was the page then there was the application
  • 10. A Brief History of the Web In the beginning there was the page then there was the application and then there was G-Mail
  • 11. Post Modern Web Applications _ feel more like a 90s area desktop application than they do feel like a web page _ talk to backend systems in highly asynchronous and bi- directional fashion _ implement complex logic within the client _ backend system must scale to large numbers of simultaenously connected users
  • 12. PMWAs _ Web 2.0 was about reapplying existing technologies to create more powerful web sites _ Ajax _ Re-Rendering only parts of a page _ „Look what we have here, letʻs make something cool with it“ _ PMWAs are about getting it right _ Wir haben die Plattform endlich im Griff.
  • 13. PMWAs Defining Features _ Realtime collaboration _ Realtime updates _ Work when offline / with flaky connections _ Application VS. Page
  • 14. Examples
  • 15. More PMWA Examples _ Google Reader/Docs/Etc. _ Youtube Realtime _ Beebo _ Papercube _ MobileMe
  • 16. FAIL _ User experience conventions for web pages fail for PMWAs _ Traditional HTML and JavaScript programming techniques do not fit PMWAs _ The HTTP request pattern does not fit the use cases of PMWAs _ Relational databases do not scale to web scale
  • 17. We need new paradigms!
  • 18. We need new paradigms! Do we?
  • 19. We need new paradigms! Do we? Yes
  • 20. We need new paradigms! Do we? Yes; but not for everything
  • 21. We need new paradigms! Do we? Yes; but not for everything I was raised by my parents with the formular conservatism = facism - 0.1
  • 22. We need new paradigms! Do we? Yes; but not for everything I was raised by my parents with the formular conservatism = facism - 0.1 Maybe I‘m a rebel now
  • 23. Some old people already know how to build rich client applications
  • 24. Some old people already know how to build rich client applications
  • 25. Some old people already know how to build rich client applications
  • 26. Lets go concept shopping!
  • 27. We need to learn from Apple how to build GUIs and let the DIN A4 page behind
  • 28. Event-Based programming provides for loose coupling in GUI programming
  • 29. We need to re-apply Model-View-Controller techniques
  • 30. We need to re-apply Model-View-Controller techniques The Flash guys are years further down this road
  • 31. Client logic needs to be responsive. We need concurrency in the browser.
  • 32. Enabling Technologies
  • 33. Disabling Technologies
  • 34. The Internet Explorer 6 Dillemma _ Progress in web development has been hindered by the need to be compatible with a 7 year old complete failure. _ This will end in 2010.
  • 35. The Internet Explorer 6 Dillemma _ Progress in web development has been hindered by the need to be compatible with a 7 year old complete failure. _ This will end in 2010.
  • 36. The Internet Explorer 6 Dillemma _ Progress in web development has been hindered by the need to be compatible with a 7 year old complete failure. _ This will end in 2010. Internet Explorer 6 is steadily vanishing
  • 37. Enabling Technologies
  • 38. Ultra Fast JavaScript _ Tracemonkey _ Squirrelfish _ V8
  • 39. Make-The-DOM-Nicer Libraries _ jQuery _ Dojo _ YUI _ etc.
  • 40. Widget Libraries _ jQuery UI _ Dijits _ YUI
  • 41. Component Frameworks _ PureMVC _ JavaScript MVC _ SproudCore _ Cappucino _ White Open Space Ready To Be Filled
  • 42. Comet _ Server-Push like technology _ Bending HTTP to itʻs will _ Long polling
  • 43. Flash _ Use where appropriate _ Video!
  • 44. Canvas _ 2D drawing in the browser _ Will have a big future _ Eliminates many Flash use cases
  • 45. Coming with HTML5
  • 46. Local Storage
  • 47. Local Storage _ Enables offline apps _ SQL database on the client side
  • 48. _ The browser knows where you are _ Especially interesting for mobile apps _ But also coming to a home near you Geo Location
  • 49. Web Workers _ Enable multi process JavaScript _ Now we can do hard calculations on the client _ without blocking the UI _ Responsiveness!!!
  • 50. Example time
  • 51. Example time
  • 52. Bespin _ an experiment to build a text editor that works in the browser _ shows what can be done with modern web browsers _ absolutely zero Internet Explorer 6 compatibility
  • 53. Goals _ Fast _ Responsive _ Ability to edit very large files _ Collaboration - edit file with multiple users _ Extensible _ Embeddable
  • 54. Show Application Thanks for the reminder
  • 55. Event-Driven _ Source-Code Examples (In Editor) _ Real-World Example _ Open-Document -> Change Syntax Coloring
  • 56. Responsiveness _ Use of Canvas _ Web Workers, WorkerFacade
  • 57. Post Modern Web Applications
  • 58. Post Modern Web Applications The tools are here (HTML5, etc). We need to professionalize their usage.
  • 59. Post Modern Web Applications The tools are here (HTML5, etc). We need to professionalize their usage. We can learn many things from the „Fat Client“
  • 60. Post Modern Web Applications The tools are here (HTML5, etc). We need to professionalize their usage. We can learn many things from the „Fat Client“ The ecosystem is catching up (Component Frameworks, etc.). We can help!
  • 61. In the next 12 months more and more websites will become post modern web applications
  • 62. In the next 12 months more and more websites will become post modern web applications The whole ecosystem of web development will need to adapt ...
  • 63. In the next 12 months more and more websites will become post modern web applications The whole ecosystem of web development will need to adapt ... ... from user experience, over design to software development
  • 64. Thank You for Listening! http://joose-js.blogspot.com http://twitter.com/cramforce