Scenarios (Experience Threads) v.3

Click here to download:
experienceThreads03.pdf (640 KB)
(download)

Another iteration on the Experience Threads that I worked out with Pauric, based on some feedback from Jakub.

This time, the threads afford multiple non-linear paths, and the thread view allows the user to edit the paths one page at a time.

As Pauric explains, 

"
to summarise the mental model of the thread view; it's a combination of a site map that the user can drill in to and start 'stitching' pages together.  The interaction is similar to yahoo pipes, the difference being that the user drags connections from page elements (of the page currently open on stage) to other pages."

Let us know your thoughts in the comments!
---
Mike Eng

Scenarios (Experience Threads) v.2

Click here to download:
experienceThreads02.pdf (523 KB)
(download)

Building off of Jakub's sketches, here is another iteration on the experience threads.

I explored placement alternatives for the experience threads within the FluidIA interface and several options for the detail of the experience threads themselves (tabs, nested tabs, boxes that highlight the current frame).

Also, I introduced a new paradigm for explaining the function of the experience threads themselves. Think of the experience threads as processes. There may be multiple processes within a project. Each process has several steps, which can be thought of as frames. Each frame has a mockup associated with it. The detail sketches illustrate this hierarchy.
---
Mike Eng

Load With Revisions

User Story: As a user of the system I need to be able to revert to older revisions of a project based on the time and date the revision is saved and by which user.

Notes: Since this is being built with collaboration in mind, a project may have more then one editor. Current loaded project would be expanded by default but allow the user to click on the other projects to expand the revision list. Highlight currently loaded project revision. Allow user to click on the undo arrow to select previous revisions or the revision item.

Posted By: Alex

Load-with-revision-list

Login - Save - Load (Alternative #1)

The ideea is to build the 3 elements - Login, Save and Login - in an uniform state once active / hover.

Jakub's first sketch: the Login is active and background is applied around it; and the Save and Load are inactive, but once moved to Save the wrap background around Save needs to include Load too, although at Login it didn't include Save or Load.

Thus, the ideea to create and wrap in background each element and to be the same regardless of what elements is chosen. The wrap background is expandable in height and width. The inactive elements are opacity 50% (example).

Posted by: Liv

Fludia-saving-1