1.
MozCamp, Buenos Aires
Saturday, April 21, 2012
Designing Firefox

2.
¡Hola!

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:

9.
“What’s your favorite color?”

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

15.
But, we used to look like this:

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

19.
Two approaches to UX design:

20.
User Centric Design
I need...
I want...
I like A more
than B!
the customer is
always right!

21.
Strong Designer
I know what you
want more than
you do!

22.
Most design teams land somewhere between
Risks:
EPIC FAILURE
Risks:
Complexity, “grey,” users lie

23.
Historically:

24.
Users lie!

25.
Users lie!

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?

29.
Design Principles?

30.
discoverability
user control
consistency
minimalism
no interruptions
new
vs
vs
vs

31.
Beyond being well-designed,
what should using Firefox feel like?

32.
Soft
Powerful
Yours

33.
Who are we designing for
(if not just ourselves)?

34.
Our users:
People whose lives or work
revolve around the internet

35.
Respecting Flow

36.
Thursday, October 20, 11

37.
Protect, but Don’t Lecture

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)

40.
Listen to Users!

41.
Measure in the Field

42.
Do What’s Right for Users No Matter Where
Idea Came From

43.
Avoid Boundary-Case Design

44.
Questions?