Sheila Mooney wrote: > + We need to design the right UI optimized for our primary target user - > casual collaborator.
I'm not sure I understand the use case for a casual collaborator accessing the file browser. Mimi defined CC thus: "We've defined Casual Collaborator as someone who comes to Cosmo UI because a Chandler user sends them a ticket to share a group Dashboard/Calendar." Why will someone with this background want/need to see a filesystem view? People adding/deleting collections seem no longer "casual" or even driven by the sharer; they are working independently. Also, it was said "there will be minimal overlap between home dir users and Casual Collaborators". This seems to further imply CC are using the file-browsing interface less than "home dir" users. I'm concerned that optimizing for the casual collaborator may lower functionality available to those really using the file browser, a different target group as I read the discussion. Therefore it seems to me that the design should be "optimized" for the target group using the planned UI, ie not the casual collaborator. I agree that the file browser should be available to all users and not confuse the casual collaborator, but user-centered design would seem to suggest optimizing for the common case. Reasonable people can of course disagree on the expected common case. I've tried my best to absorb the thread, as others no doubt have as well. -- Jared _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ Open Source Applications Foundation "Design" mailing list http://lists.osafoundation.org/mailman/listinfo/design
