[[BackLinksMenu]] [[PageOutline]] = Usability Issues = == 0. Introduction == This page is to focus on broader areas of Sophie 2 functionality which impact product usability.; this page is purposefully not focused on the level of individual tasks. I've focused on several major sections of Sophie's functionality and added use cases to make it clear how these issues will appear in the real world. A subsection (name TK) discusses how well this works in the current version of Sophie 2 and suggests things that might need to change. This page will be expanded as usability testing begins. == 1. Timelines == Importance = high. (See Steve's page [wiki:TIMELINES here].) === 1.1. Time-based media on a page === (usecase: people want to put a video or audio file on a page and have it work without messing with timelines more than they have to.) === 1.2. Slideshows === (usecase: people have a bunch of pictures which they want to have on sequential pages; while the pages turn, there's audio. More complicated version: same thing, but with video that goes through the pages rather than audio (the video section of the Mozart book).) == 2. Page templates == Importance = high. Related issues: copying/pasting frames; shared frame/shared content problem. Does locking content help things? Can this be made comprehensible? === Current implementation === While there is some page template functionality, it's not in its final state, and it's hard to gauge how well it will work. Another problem is the lack of flows. == 3. Frames and flows == Importance = high. This is essentially the problem of basic users wanting to use text that spans pages. Possibly immense related problem: interaction between flow frames and page templates. === Current implementation === Right now we don't have a way to use flows on the same page or across pages. === Use case 1: standard book with single flow frame === (How do we instruct people how to do this? Do they set the page up, then insert the text? What if they insert the text, then set up the page, then want subsequent pages to use that layout?) === Use case 2: book with parallel flow frames === === Use case 3: book with several flows in series === Chaptering: does this merit a separate section? Obviously not going to be in there, but it is something people are going to want in some form. == 4. Sophie Server integration == Importance = medium. == 5. Book templates == (how important are these?) == 6. Anchoring == Importance = medium. == 7. Show/hide issues == (do we need to dig this up again?) == 8. Text styles == (confusion between character & paragraph application.) == 9. Bug reporting == (See [wiki:UserBugTracking my user bug tracking page]. Not sure if this should actually go in here; but maybe the part about reporting in the app goes in from a usability standpoint - this is something we should be getting feedback on.) == 10. Resource handling == (basically: dealing with large numbers of resources in a book; sorting, filtering; importing everything at once. If we don't have drag and drop, this could become an issue to solve.) == Comments == (add comments here)