On Thu, Sep 10, 2009 at 2:02 PM, Joshua Muskovitz <[email protected]> wrote:
> For the same reason your car isn't a daiquiri. > I don't think this is a valid analogy. I think Kim's original questions points to the current blurring of lines that's happening between the previous dichotomy of apps vs. browser environments. You have more and more applications that do live in the browser or in the cloud, as well as hybrid environments like Adobe AIR, which are browser-based apps ported to the desktop. And we've also got HTML 5 on the horizon, which will allow us to do things in the browser (such as local data storage) that have previously only been possible in desktop environments. Finally, you've also got mobile application environments, which seem to be largely shifting over to a standardized WebKit browser platform. All of these changes lead to questions like, "why isn't the OS a browser?" and I think, as interaction designers, we need to think about what the browser really is to a user. Up until now, it has denoted "the web", which was a separate place from everything else. But as everything is increasingly part of the web, does it make any sense to have a conceptually separated environment for it? Alexis ________________________________________________________________ Welcome to the Interaction Design Association (IxDA)! To post to this list ....... [email protected] Unsubscribe ................ http://www.ixda.org/unsubscribe List Guidelines ............ http://www.ixda.org/guidelines List Help .................. http://www.ixda.org/help
