SlideShare uses cookies to improve functionality and performance, and to provide you with relevant advertising. If you continue browsing the site, you agree to the use of cookies on this website. See our User Agreement and Privacy Policy.
SlideShare uses cookies to improve functionality and performance, and to provide you with relevant advertising. If you continue browsing the site, you agree to the use of cookies on this website. See our Privacy Policy and User Agreement for details.
Successfully reported this slideshow.
Activate your 14 day free trial to unlock unlimited reading.
3.
Correction:
The user experience workshop tomorrow is at
11:30am in Storni - not at 5:15pm!
4.
My Name is Boriss
I’m on the Mozilla User Experience Team
5.
I’m going to talk about:
• What user experience is
• Design and user experience at Mozilla
(including what we’ve gotten wrong)
• The glorious future
6.
Our focus is on how Mozilla’s products and
services are perceived, learned, and used
7.
Fixing current
problems
Designing
new products
and features
User experience
8.
• Design limited: based on annoyances,
not possibilities
• “Averaging” user needs
If only current UX problems are considered:
10.
Our goal is designing based on user needs
• What are users trying to accomplish?
• What are their metrics of success?
• Who are they?
11.
Many ways of determining user needs
• User testing and interviews
• Data analysis (eg Mozilla Test Pilot & Telemetry)
• Focus groups
• Contextual inquiry
• Eye-Tracking studies/observational studies
• Analyzing feedback
12.
User experience design at Mozilla
began after Firefox
13.
First “user experience” at Mozilla
=
hackers creating a browser for, well, them
(and this is awesome)
14.
“Scratching an itch”is important for Mozilla,
open source, hacking culture
16.
ewdwe
Now, we look more like this:
(~30,000 million of us)
17.
We can’t design for millions
the same way we did for only ourselves
18.
Partially, the UX team’s goal is to make sure
that UX at Mozilla:
1. Is coordinated, cohesive, directed
2. Still happens true to Mozilla’s organic, open,
itch-scratching character
26.
So, we’re open source.
We like scratching our itches.
But we also need coherent design for our
millions of users.
27.
“I love tabs!”
“Everyone uses tags,
not bookmarks.”
“My mom doesn’t
understand tabs.”
“OpenID is the future!”
“Nobody uses the
‘Go’ button.”
“There should be
a preference setting.” “Add support for
BitTorrent.”
!
“I only use keyboard
shortcuts.”
“Add support for
Ogg Vorbis.”
“That’s great!”
“That’s awful”
“The profile manager
should be redesigned.”
“Closebuttons are better at
the end of the tabstrip.”
“The URL bar should
be removed.”
“This looks too
much like Chrome!”
28.
• Have add-on infrastructure to explore new ideas
• Elevate contributors who know what they’re doing
• Focus on design principles
Wat do?
38.
Protect, but don’t lecture
• You can’t “teach people how security works”
• Maintain blacklists for add-ons & plug-ins
• Don’t ask people to do work
39.
Be a good fit
- visually and interactively -
across devices
(we don’t do this well right now)