The desktop is an application

Had a brief discussion on twitter the other day where people (@simoncrosby, @joeshonk, @RichCrusco) were saying that we only need to focus on delivering applications and NOT a Windows 7 desktop. I completely disagree. In fact, we should be treating the desktop interface as an application. Of course the desktop-haters immediately came out saying “No, the desktop is not an application.” This was pretty much what I expected.

Unfortunately, trying to explain my point in 140 characters wouldn’t do it justice but a blog is a start.

The key point is that we need to focus on the users. When you look at how users work with these systems, you understand what they need in order to work effectively. We look at the applications as a way to get to the data. We decide if the user needs access to the application, and it is either granted or denied. If we ignored the desktop interface, things would be much easier. I already have a desktop interface, so why do I need another. My local desktop interface has my own applications, so simply let me subscribe to virtual applications. This would alleviate the user-installed application challenge. If you only focus on the applications, you are missing an important aspect because this model doesn’t work for everyone. Let me give you some examples for and against having the desktop interface delivered:

  • iPad: I don’t want to use the Windows desktop interface on my iPad as it doesn’t feel natural (Windows 8 might change this, but will wait before deciding). On the iPad, I just want to get to one or two of my applications. So in this case, I want to ignore the desktop interface.
  • Work-shifting: I work remotely on my company-owned laptop (Windows 7). If IT only gave me applications, things would feel unnatural. They could populate my start menu with my apps, but it wouldn’t feel right. I would need 2 Windows Explorers (one on my personal desktop and one for my virtualized environment). I would need two browsers (one for my personal and one for my virtual). Which one do I use? I’m not on the internal network, so I need to make sure I use the right one. Not user friendly and very unnatural. In this case, the Windows desktop is a requirement as it makes the user experience better.
  • BYO: A user brings their device and uses it at work. From a technical perspective, delivering virtualized applications would work fine. Unfortunately, we aren’t looking at the user perspective. A user will not want corporate applications on there. They don’t want those applications to consume hard drive space, nor do they want it polluting their start menu. Virtualizing the applications could overcome these issues, but the user’s perception is that the applications are local. Even training the users about application virtualization would not be enough as many users believe big brother is still watching. Plus, there will be confusion of having the corporate web browser and your local web browser (I hope you are using the right one, or you might get into trouble). Users in a BYO program want to use their own device, but still be given a “Corporate” environment to work on.
  • Local Corporate Device: You have a physical desktop (running Windows 7) located on the corporate WAN, so why do I want to deliver another desktop interface on the one I already have? You probably don’t, so simply deliver applications.

We love to talk about being able to do all of these cool things with virtualization and what the future will hold, but people tend to ignore the typical user and their perspective. This perspective and the comfort of using the system are what makes things succeed or fail. If the solution doesn’t feel natural, it won’t work. And I say that only focusing on applications and ignoring the desktop interface, you are ignoring the user and only thinking about some pie in the sky utopia.

If we treat the desktop interface (XP, Windows 7, RDS) as an application, you must assess the need for the interface using the same criteria you use for applications (end point device, user usage requirements, location, etc). If you treat the desktop as a desktop, you will surely go down the road believing the desktop interface is irrelevant only to find that users are unhappy with the application virtualization solution, thus killing user acceptance.

Not everyone requires a corporate-delivered desktop interface, but many do and we cannot ignore this need.

Daniel – Lead Architect
XenDesktop Design Handbook

4 thoughts on “The desktop is an application”

  1. “Getting used to ” is a time bound thing. Since until absolutly necessary we do not want to manage two environments’ 1 for Desktop and 2 for Xen App.. we need to slowly make users migrate from 1 Desktop and XenApp environment which is easy to manage and since anyway apps are moving to cloud’s that will be the future as well..


  2. Nice Post and I agree completly on focusing on the big picture when the user is the central interest as he’s the heart of the production that make the add value at the end…

    Focusing on applications and ignoring the desktop will at the end, fail the virtualization approch to the desktop areas… We need as architects to deliver a well packaged solution, easy to use and natural off course, so the user will continue to work better than before with more freedom and collborativ way, i think!

    I have many of my clients asking me the same question, Why do we need to virtualize the desktop? why not just review the solution for the application…

    the user interface and experience is the most important aspect of progressing productivity and will not be achieved if skipping the desktop layer.

    so I completely agree with you Dan

    keep the good work



Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

This site uses Akismet to reduce spam. Learn how your comment data is processed.