[tahoe-dev] barriers to using tahoe
nathan at atlasnetworks.us
Mon Feb 1 19:25:21 UTC 2010
Generally, UI work requires use-study, design work, analysis, and careful, structured implementation. There is apparently $400 on the table for anyone who wants to work through that whole process. Simply identifying 'optimal user experience' (where optimal really just means 'your average joe won't give up on it after 2 minutes') is probably weeks of work, or more, to do correctly. Even then, you'll never please everyone, but that's life.
Step one, IMHO, is to identify what specifically, for joe-user, is weak (read: not intuitive/user friendly). The end goal, at least for me, would be to see a UI/presentation layer that wraps the WAPI functions into something very friendly (read: my little sister could use it).
Is there an existing issue open, or a location we could use, to outline various UI related pain-points, in a way that would be useful to the developers?
Sr. Systems Administrator - Atlas Networks, LLC
office: 206.577.3078 | suncadia: 206.210.5450
www.atlasnetworks.us | www.suncadianet.com
> -----Original Message-----
> From: tahoe-dev-bounces at allmydata.org [mailto:tahoe-dev-
> bounces at allmydata.org] On Behalf Of Raoul Duke
> Sent: Monday, February 01, 2010 10:54 AM
> To: tahoe-dev at allmydata.org
> Subject: Re: [tahoe-dev] barriers to using tahoe
> On Mon, Feb 1, 2010 at 9:40 AM, EdPimentl <edpimentl at gmail.com> wrote:
> > Define the user optimal user experience ...
> i think that phrase is fraught with peril.
> there is no optimal user experience in some sense; there are too many
> different needs to balance to define anything. in my mind, good
> usability is all about making trade-offs over time across all possible
> use cases. the best you can write down is something like "the user can
> successfully accomplish tasks, and the user reports they are happy
> with the experience." if you try to get more detailed than that (with
> more than like 1 single user) you are going to quickly get into
> conflicting interests, abilities, goals, etc. which all have to be
> in other words: if there is not an experienced user experience person
> working on the project, then the chances of getting something as
> complicated as this to be an "optimal user experience" is nil. hire
> somebody :-)
> no i'm not a ux person by trade, only by end-user-suffering
> tahoe-dev mailing list
> tahoe-dev at allmydata.org
More information about the tahoe-dev