Re: [agile-usability] Product Metaphor
- On Mon, Jul 26, 2010 at 7:31 AM, Jared Spool <jspool@...> wrote:I guess that was my point.
Now that we have a well-established music metaphor, we've had a few requests for "bookmarks." :-)
If you're using the metaphor as a way to brainstorm functionality and features ("if our software was a car, what would it be like?"), that works, because you don't have to be dogmatic by sticking with the metaphor.
However, if you try to build it out as a UI, you run into issues where the metaphor doesn't support the innovation (because if you did, you wouldn't be replacing it).Hi Jared,I'm not sure. I think it depends on how dogmatic one is.For example, we're likely going to experiment with a "save this (or my) location" link on pages in our eLearning. Will that break our music metaphor? A bookmark symbol would surely break it, while a simple link may be just fine (though the users will ultimately be the judge).
This is the current argument many designers have against Apple's iPad & iPhone design, where elements, like the calendar and notebook, have real-world metaphorical references to their traditional form factors (think the spiral "binding" and yellow lines on the notepad). Their argument is that it's holding back on what the design could be.Not sure about calendar, but notebook feels refreshingly simple and so easy to use for quickly storing/pasting notes on iPad/iPhone. I don't see what kind of innovation one would need from it, though I am low on sleep.
The counter to their argument is that you need to ground the design in something users are familiar with. If it's too novel, then they can't grok it, because none of their previous experience helps them with the new interface.I do wonder why we can't "save locations" in music - why is that only limited to books and bookmarks? Maybe because older music players couldn't support such a feature. Surely iTunes could easily record a saved location inside a song (or sound file) and store that location for easy retrieval. Seems to support the idea that the metaphor is holding the designers back, yet it need not be the case, at least in this example.
So, it's a hard line to tow: make it like existing real-world elements (the metaphor approach) or innovate?Tough choice. Both would be nice!bestjk
- On 07/26/2010 10:31 PM, Joshua Kerievsky wrote:
> I do wonder why we can't "save locations" in music - why is that onlyiTunes certainly could do that if they wanted, and some other audio
> limited to books and bookmarks? Maybe because older music players
> couldn't support such a feature. Surely iTunes could easily record a
> saved location inside a song (or sound file) and store that location
> for easy retrieval. Seems to support the idea that the metaphor is
> holding the designers back, yet it need not be the case, at least in
> this example.
players definitely do. Not just modern MP3 players, either; some CD
players offered bookmarking features. Even the first CD player had A->B
looping, a primitive bookmarking, and it also had track indexes, a
system for in-track skip points that has since fallen into disuse. I
think that suggests why iTunes doesn't have bookmarking: most people
don't want to do that with music.
With novels and other linear reads, people will use a placeholder, so
the iPod does keep track of where you left off in audiobooks and
podcasts. Serious bookmarking, though, mainly happens with non-linear
books, like textbooks and references. Those aren't popular as
audiobooks, presumably because of audio's essential linearity.
So I don't think it's the metaphor that is holding the designer back in
this case. It's the medium, and the user's desire.