Any insights on shifting context?

18 Jan 2006 - 1:59pm
8 years ago
2 replies
469 reads
John Vaughan - ...
2004

At my current gig we are developing IxD for a "bulletin board" feature that allows you to get to the same message record from several different areas of the site.

The current client wisdom is to store the target message pages in a subsection under tab "Z". You can get to message pages from source webparts that may be on several different pages under several different other tabs.

It is not possible to store the message as a part of the webpart (i.e. embedded in the source page) and the client will not open the target message in a separate browser window.

The UX result is that - when you drill down to the target message from Page "A" under tabfolder "X" - the target message is displayed under tabfolder "Z". When you exit the target message page, you return to Page "A" under tabfolder "X". Alternatively, you might get to the same target message from Page "B" under tabfolder "Y". Or even from Page "C" under tabfolder "Z". And so on...

So sometimes the tabfolder of the target message page changes - and sometimes it doesn't, depending on wheere you're coming from.

Does anyone have any insights on whether this "changing context" has any impact on the UX? Do customers get confused? Are there better solutions?

John

Comments

19 Jan 2006 - 2:17am
Oleh Kovalchuke
2006

> Does anyone have any insights on whether this "changing context" has any impact on the UX? Do customers get confused?

I have seen "changing context" before - it is indeed confusing.

> Are there better solutions?

How about this:
a) Display links to the messages with clear indication "you are going
to section Z".
b) At the target page "this content is linked from sections X, Y and
Z", where X, Y and Z are back linked to correct sections?

Or why not let the machine do the work and build three target pages
with identical copy under tabfolders X, Y and Z for the three use
cases you have described?

--
Oleh Kovalchuke

On 1/18/06, vaughan1 at optonline.net <vaughan1 at optonline.net> wrote:
> [Please voluntarily trim replies to include only relevant quoted material.]
>
>
> At my current gig we are developing IxD for a "bulletin board" feature that allows you to get to the same message record from several different areas of the site.
>
> The current client wisdom is to store the target message pages in a subsection under tab "Z". You can get to message pages from source webparts that may be on several different pages under several different other tabs.
>
> It is not possible to store the message as a part of the webpart (i.e. embedded in the source page) and the client will not open the target message in a separate browser window.
>
> The UX result is that - when you drill down to the target message from Page "A" under tabfolder "X" - the target message is displayed under tabfolder "Z". When you exit the target message page, you return to Page "A" under tabfolder "X". Alternatively, you might get to the same target message from Page "B" under tabfolder "Y". Or even from Page "C" under tabfolder "Z". And so on...
>
> So sometimes the tabfolder of the target message page changes - and sometimes it doesn't, depending on wheere you're coming from.
>
> Does anyone have any insights on whether this "changing context" has any impact on the UX? Do customers get confused? Are there better solutions?
>
> John
> ________________________________________________________________
> Welcome to the Interaction Design Association (IxDA)!
> To post to this list ....... discuss at ixda.org
> List Guidelines ............ http://listguide.ixda.org/
> List Help .................. http://listhelp.ixda.org/
> (Un)Subscription Options ... http://subscription-options.ixda.org/
> Announcements List ......... http://subscribe-announce.ixda.org/
> Questions .................. lists at ixda.org
> Home ....................... http://ixda.org/
> Resource Library ........... http://resources.ixda.org
>

19 Jan 2006 - 3:34pm
Juan Lanus
2005

In my Gmail account I see any single message in different contexts
like inbox, search results, ...
I would do it with programming, the AJAX way.
The "thing" (I refrain to call it "page") can store messages as such
into it's bowels, and display them as required, in any context. As mi
Google mail does.
--
Juan Lanus
TECNOSOL
Argentina

Syndicate content Get the feed