The Traditional Desktop ( The Processing Box )

• Software ( OS and Apps ) is very influential but general idea for end-user is “It’s a Processing Box”
• Operating System is the main end-user app. End users were nerds ( participating users actually .)

• The physical aspect of newer devices also contributes to the end-user perception and impacts usage.

The New Desktop ( The Flow Medium )

• It’s not in the physical – but everywhere accessible ( as in the Web );
• Yet the physical is the input or output;

Browsing Medium

• From the Traditional Desktop to the Inner Desktop, the Connected Desktop where information and connectivity is active in the usage scenario.
• To the right tends to higher flexibility in interoperation, convergence to the information and meaning.
• To the left it offers a foundation and supporting platforms.

Input and Output Media

• Output media is flexible; What seems to be a lead to do it for a fixed size is just a perception of the physical size.
• Newer devices are to have stretchable screens.

• Old desktop model: Input Device model with limited devices suited for a Table: Mouse, Keyboard.
• Desktop everywhere model: Input device is life. Devices to serve as proxies and add events to the experience: GPS, temperature, time-agenda, camera photo, voice input, pen input, keyboard input, 3d motion input ( Wee like input ), and more.
• The environment itself also to add to the experience. The restaurant Menu to broadcast; New Valley city clock to offer its history of time.

Browsing the Web

• Access ( Data )
  • Web 90-94-00, Access to the Resource Data
  • End of the period begins Standards: DOM, CSS, XML, XHTML
  • End-user mere end point, blames developer;
• Application ( Processing )
  • DOM reaches developer world,  Event model bubbles up;
  • 2003 – Inner-Browsing;
  • 2005 – AJAX goes wild;
  • Google Maps, Google Gmail, Google API development starts;
  • End-user: Uses; Developer listen to the users;
• Events ( Flow )
  • 2006 – Microformats
  • The Node is in evidence; with meta-deta and associations with referenced resources;
  • Events to reach external Web Services and as well internal mechanism for the Browsing Experience;
  •  End-user: Becomes the part user. User manipulates information directly and the information lifecycle and usage defines requisites to the execution platform.