[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [GMG-Devel] Feature design

From: Joar Wandborg
Subject: Re: [GMG-Devel] Feature design
Date: Sat, 03 Nov 2012 10:35:22 +0100
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:10.0.10) Gecko/20121027 Icedove/10.0.10

On 11/02/2012 11:51 PM, Jef van Schendel wrote:
> Hi!
> Two quick notes:
> 2012/11/2 Christopher Allan Webber <address@hidden
> <mailto:address@hidden>>
> >    To paraphrase, he observed that
> >    lately we've been having a "someone picks a feature and implements it
> >    and then afterwards Jef van Schendel runs in and tries to clean up the
> >    look of things" approach.  Is this really the right way? 
> I think it's important to note that it's not just the look of things. I
> don't mind "cleaning up afterwards" when it comes to the graphical bits,
> because doing so is easy enough. However, the interaction design side of
> things is not only more important, but also much harder to change
> after-the-fact.

I very much agree with this, what we have to figure out is how to
mock-up user experience beforehand. I guess writing/user stories is the
most usable option.

> >      - We do want a more designed-first development process.  However that
> >       doesn't just mean graphic design, it's also technical design.
> >       Rushing into a design without thinking about the user experience is
> >       bad.
> Another thing Aaron talked about in his mail (Aaron, stop me if I'm
> misconstruing your ideas here!) was that it's hard to know what we're
> actually designing towards. We tackle individual features, but it's not
> clear what the higher-level plan is. This can make it very hard to make
> (correct) decisions, especially as MediaGoblin matures.

We have some usecases in the wiki, I can only find one[1] at the moment.
However, this does not really reflect my opinion on how MediaGoblin is
used most effectively. And as things grow more complex and new features
are added, it might be great to describe at least the expected default
usecase, so that we hopefully can share that vision between eachother.

> Jef
> _______________________________________________
> devel mailing list
> address@hidden


reply via email to

[Prev in Thread] Current Thread [Next in Thread]