It’s been a little while since the last piece of code made it to github, or a sketch has been drawn up. Nevertheless, a proper first release that’s working and useful would be nice some day. So I began thinking that perhaps I took a too big of a piece to chew. With that, it’s back to square one and rethinking what should be in and what should be out. Here is a step back with a refactoring mentality, along with a working draft of what this tool could be for the first release. Thoughts?
Sketches & Scenarios
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.
Here are a few new ideas on how to improve the existing scenario functionality. Each corresponding letter denotes an alternative idea. Just thought to throw this out here and see if some concepts seem better than others. There are at least three directions which I’d like exercise in the next revision behind scenarios. These include:
- Allow quicker access to creation of scenarios (one click to create a new scenario)
- Separate of scenarios from the left toolbar to the topbar (because it’s bigger than tools)
- Allow playback of scenarios
I’ve also moved Scenarios out of the 0.1 release and moved it into the 0.2 release on our roadmap. Thoughts?
When users save a project as a URL, multiple access points should be shareable. Some users might wish to share the full project, others might wish to draw attention to a particular page, while others might wish to share an experience thread. Here is a draft spec for distinguishing the various URL types for loading the project. Of course if a user is not logged in, they will not have the permissions to switch from the “present” mode to the “design” mode (and of course they will only have read only permissions).
Pauric just shared an updated PDF sketch for the clipboard interaction. Thought I’d share it publicly. It contains some new drag and drop interactions for pasting as instance and master. Also supports different item types such as pages, objects and form elements. Awesome work! Will comment on it below.
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
Just found this and thought perhaps we could combine the login / register interface into one. Perhaps we could even auto detect the email field if it exists or not onChange to get the form to react in realtime showing either a “login” or “register” button.