On Tuesday, 22 December, 2009 10:58 AM, Leisa Reichelt wrote:
yes, it just looks like an ordinary computer screen. There
is a little icon in the top of screen that you can use to stop/pause
Silverback but it's unobtrusive, up there with the date/time etc.
I know now! let's do it the way Istanbul and gtk-recordmydesktop do it.
There's a panel icon that you click to start recording the session (
http://www.ubuntu-pics.de/bild/35152/screenshot_031_yg2Pfb.png ). When
it's started, it turns into
http://www.ubuntu-pics.de/bild/35153/screenshot_032_g2P0s8.png .
I have to say that, at times, I would like to have the ability
to switch on an observe option in silverback - I am a big fan of
getting stakeholders to observe testing live (although I tend to use
silverback when I'm out the the field an observation is less
practical). I have dreams of being about to stream the sessions live so
that others can view them from their desk whilst I'm out researching
wherever I like. There's more than software to worry about there tho!
That's a good feature to have. After all, the researcher can just
choose to use it or not to use it. However, if it is technically hard
to develop this feature, we can postpone this for later versions. If
it's easy to implement, by all means, let's have it. It's just that, if
all stakeholders have to pay attention to the testing while it's being
done, it could be time-consuming for a lot of people because a session
can involve a lot of pausing. After all, the quality of the video
wouldn't improve if they watch it live. You can just email the video
when it's done so they can watch it during their own time.
agree re: visualising mouseclicks - this is useful and clients
tend to like it a lot.
re: controls for stopping/pausing the session - personally I don't tend
to use the apple remote for these tasks, I just take control of the
computer :) (the test is being disrupted for one reason or another so
it doesn't tend to be a problem). What you *can* do with the remote in
Silverback that is very useful is to be able to mark points of interest
so you can go back and take clips from the video at a later date. This
is a great timesaver, and I'd recommend that we try to work this in
somehow. The advantage of using the remote to do this is that it is
unobtrusive so you're not telling effectively telling the participant
'you're doing something very interesting now', but perhaps using an
outlying key on the keyboard would be an acceptable alternative, given
that we don't have the 'remote' option? (unless we can do something
fancy with bluetooth + mobile phone... or that could be me dreaming
again!)
As I mentioned, I think, it's best to have the little panel icon to
record and stop :)
re: what we call them - I've always preferred 'participants'.
Great! :)
________________________
Leisa Reichelt
Disambiguity.com
Freelance Contextual Research, User Centred Design & Social Design
leisa disambiguity com
+44 778 071 2129
2009/12/22 Allan Caeg <allancaeg gmail com>
Cool.
How does the tester's screen look like while the testing session is
running? Does it look like an ordinary computer screen or is there any
trace of Silverback?
Now, I think, an "observe" feature isn't needed. First of all, it would
be hard to implement. It's also hard to gather all stakeholders for
them to view testing sessions while it is running and if the tester
finds out, that would be awkward for him or her.
I have new features in mind. I saw a morae session once. On playback,
it highlights where the mouse is. Silverback also shows if the tester
clicks the mouse. That would be a cool feature to have.
We have to figure out how to control sessions, though. Without an
observe feature (where I think, we can control the running session),
how are we supposed to be able to pause and stop the session?
Silverback does it with an Apple remote. I think, it's best if we just
settle with something much simpler like having keyboard shortcuts for
play, pause, and stop?
Btw, let's just not call our testers "test subjects" like how
Silverback people call them. As a psych major, I was disturbed. Let's
call them "testers" or "participants" :D
On Tuesday, 22 December, 2009 10:15 AM, Leisa Reichelt wrote:
oh look, here's one they prepared earlier
:)
it's a little bit salesy but gives you a good walk through
of
the UI
________________________
Leisa Reichelt
Disambiguity.com
Freelance Contextual Research, User Centred Design & Social Design
leisa disambiguity com
+44 778 071 2129
2009/12/22 Allan Caeg <allancaeg gmail com>
Hello Leisa!
Thanks for the input. I'll be happy to see a screencast of that app.
They may be a free trial, but I don't have a Mac to test it :)
Best Regards,
Allan
On Tuesday, 22 December, 2009 10:05 AM, Leisa Reichelt wrote:
hi guys
new to this list, so hope you don't mind me adding my 2c
here -
just wanted to check that you've taken a look at silverbackapp.com
as a reference interface for this project. It doesn't have an observer
mode, just runs usability test capture (screen capture + headshot) from
a Mac, but has a fairly nice, simple admin UI - worth a look and I
think you can get a 30 day trial for free. If not, sing out and I'm
happy to do a screencast of my installation.
hope that helps and good luck with this project - it's
definitely needed!
Leisa
________________________
Leisa Reichelt
Disambiguity.com
Freelance Contextual Research, User Centred Design & Social Design
leisa disambiguity com
+44 778 071 2129
2009/12/22 Allan Caeg <allancaeg gmail com>
Maybe, on the welcome
screen,
we can just use something like what I
proposed earlier ( http://i.imagehost.org/0753/welcome.png
) then when the user selects the project he wants, he'll see all the
sessions there.
That would create less visual noise, because you wont see every session
from different projects on the welcome screen. After all, if you have a
session in mind, you know what project contains it. :)
By the way, there's a GNOME 3 usability hackfest on feb 22-26. Ivanka
is going to be there too. I think, this project deserves some attention
there. After all, they're talking about Pongo there ;)
Allan
On Monday, 21 December, 2009 02:38 PM, Natan Yellin wrote:
OK. I was thinking that we could always
show
individual sessions and just group them under project headings.
Something like:
Recent Sessions:
* Project 1
- Session 1
- Session 2
- View All
* Project 2
- Session 1
- Session 2
- View All
* View All Projects
On Mon, Dec 21, 2009 at 8:32 AM,
Allan
Caeg <allancaeg gmail com>
wrote:
Good question.. I
was
thinking that it's going to be one project. A
project is a group of related sessions. I just don't know if that's
technically feasible. If it's not it's just going to be one session.
On Monday, 21 December, 2009 02:29 PM, Natan Yellin wrote:
Yes.
I don't know much about usability testing, so is each entry in "Recent
Projects" a group of related sessions or just one session (e.g. one
user)?
Natan
On Mon, Dec 21, 2009 at 5:50
AM,
Allan
Caeg <allancaeg gmail com>
wrote:
Like this
one? http://i.imagehost.org/0753/welcome.png
:)
Got the idea from Brasero http://www.ubuntu-pics.de/bild/35029/screenshot_030_sw8XCE.png
On Monday, 21 December, 2009 05:14 AM, Natan Yellin wrote:
Whoops, I hit the send button too
soon. :)
What about an overview window with buttons like:
[View a past session] [Record a new session]
Clicking on [Record a new session] would open up a window with some
default settings. The user would then click on a [Create Session]
button afterwhich the window would be the same as if it was opened with
[Record a new Session]
On Sun, Dec 20, 2009 at
11:09
PM,
Natan
Yellin <aantny gmail com>
wrote:
What about an overview window
with
buttons
like:
[View a past session] [Record a new session]
After clicking on [Re
On Sat, Dec 19, 2009
at
10:19
AM,
James
Moschou <james moschou gmail com>
wrote:
> What app did you use to make this
mockup? :)
Gtk Builder/Glade
Also I agree that a wizard would not work. I just didn't want a
prepare/setup tab that would become useless once the recording has
started.
_______________________________________________
Usability mailing list
Usability gnome org
http://mail.gnome.org/mailman/listinfo/usability
|
