User Experience Desktop Context for Applications

I have a serious question.

For a specific enterprise vertical. Would the desktop environment context work better for overall improvement in user experience and user effectiveness. Something that you would see on a graphical desktop environment? A Task Bar that holds the tabs or buttons for the open applications and documents, folders on the desktop will store respective information.

For example, if there is a folder called Mail, I double-click on it, I see all my emails there, as single documents, or maybe if I’ve organized them I use the folder view context. Or maybe a folder called Contacts, which actually displays avatars/profile pictures of my contacts from all subscribed social networks. Or, you know, whatever.

It might not work well for the generic audience, but would it work for a specialized industrial vertical? Could it work?

I know a lot of people who rely on folders and documents to organize and store information. Very few people I know who use single tool/application to organize everything.

In other words, will hiding one layer of interface from the end-user work.

The Desktop Metaphor vs The Application Metaphor

I am deliberately being vague here, but humor me on this.

Real life example:

While looking at various version control systems, I went through two basic experiences. The first was a middle layer application that I had to integrate with my main application. I had to specify check-outs and check-ins, make sure that the file list that the version-controller was showing me was really the latest. It was pretty much straightforward and effective once I got the hang of it. The second presented me with a different user experience, rather the opposite, it offered a user experience that I was familiar with, the folder view. My project documents were stored in a folder, all I had to do was point my document authoring applications to this folder and that was the end of it. To check out a file, I pull up the context menu to get not only the standard options, but also the additional version control options.

The difference in my experience was removing the version control layer of sand-boxing out of my immediate access. The folder was a representation of the project, which was guaranteed by that version control to always let me access the latest versions of the documents. It was less intrusive, so I enjoyed it more. Firstly because it allowed me to stop thinking too hard about which revision of which version of which fork in the project I have to choose, secondly, it allowed to stay inside my learned desktop environment context, i.e. the Folder-document hierarchy.


About khansalmanahmad
A technology and solutions specialist who at times dabbles in philosophy. Is interested in learning new things. Gets really excited by and looks forward to "WOW" experience.

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

%d bloggers like this: