Planet UX

Updates from the Firefox User Experience Team

July 13, 2017

Firefox UX: Firefox Workflow User Research in Germany

Munich Public Transit (Photo: Gemma Petrie)

Last year, the Firefox User Research team conducted a series of formative research projects studying multi-device task continuity. While these previous studies broadly investigated types of task flows and strategies for continuity across devices, they did not focus on the functionality, usability, or user goals behind these specific workflows.

For most users, interaction with browsers can be viewed as a series of specific, repeatable workflows. Within the the idea of a “workflow” is the theory of “flow.” Flow has been defined as:

a state of mind experienced by people who are deeply involved in an activity. For example, sometimes while surfing the Net, people become so focused on their pursuit that they lose track of time and temporarily forget about their surroundings and usual concerns…Flow has been described as an intrinsically enjoyable experience.¹

As new features and service integrations are introduced to existing products, there is a risk that unarticulated assumptions about usage context and user mental models could create obstacles for our users. Our goal for this research was to identify these obstacles and gain a detailed understanding of the behaviors, motivations, and strategies behind current browser-based user workflows and related device or app-based workflows. These insights will help us develop products, services, and features for our users.

Primary Research Questions


In order to understand users’ workflows, we employed a three-part, mixed method approach.


The first phase of our study was a twenty question survey deployed to 1,000 respondents in Germany provided by SSI’s standard international general population panel. We asked participants to select the Internet activities they had engaged in in the previous week. Participants were also asked questions about their browser usage on multiple devices as well as perceptions of privacy. We modeled this survey off of Pew Research Center’s “The Internet and Daily Life” study.

Experience Sampling

In the second phase, a separate group of 26 German participants were recruited from four major German cities: Cologne, Hamburg, Munich, and Leipzig. These participants represented a diverse range of demographic groups and half of the participants used Firefox as their primary browser on at least one of their devices. Participants were asked to download a mobile app called Paco. Paco cued participants up to seven times daily asking them about their current Internet activities, the context for it, and their mental state while completing it.

In-Person Interviews

In the final phase of the study, we selected 11 of the participants from the Experience Sampling segment from Hamburg, Munich, and Leipzig. Over the course of 3 weeks, we visited these participants in their homes and conducted 90 minute interview and observation sessions. Based on the survey results and experience sampling observations, we explored a small set of participants’ workflows in detail.

Product Managers participating in affinity diagramming in the Mozilla Toronto office. (Photo: Gemma Petrie)

Field Team Participation

The Firefox User Research team believes it is important to involve a wide variety of staff members in the experience of in-context research and analysis activities. Members of the Firefox product management and UX design teams accompanied the research team for these in-home interviews in Germany. After the interviews, the whole team met in Toronto for a week to absorb and analyze the data collected from the three segments. The results presented here are based on the analysis provided by the team.


Based on our research, we define a workflow as a habitual, frequently employed set of discrete steps that users build into a larger activity. Users employ the tools they have at hand (e.g., tabs, bookmarks, screenshots) to achieve a goal. Workflows can also span across multiple devices, range from simple to technically sophisticated, exist across noncontinuous durations of time, and contain multiple decisions within them.

Example Workflow from Hamburg Participant #2

We observed that workflows appear to be naturally constructed actions to participants. Their workflows were so unconscious or self-evident, that participants often found it challenging to articulate and reconstruct their workflows. Examples of workflows include: Comparison shopping, checking email, checking news updates, and sharing an image with someone else.

Workflows Model

Based on our study, we have developed a general two-part model to illustrate a workflow.

Part 1: Workflows are constructed from discrete steps. These steps are atomic and include actions like typing in a URL, pressing a button, taking a screenshot, sending a text message, saving a bookmark, etc. We mean “atomic” in the sense that the steps are simple, irreducible actions in the browser or other software tools. When employed alone, these actions can achieve a simple result (e.g. creating a bookmark). Users build up the atomic actions into larger actions that constitute a workflow.

Part 2: Outside factors can influence the choices users make for both a whole workflow or steps within a workflow. These factors include software components, physical components, and pyscho/social/cultural factors.

Trying to find the Mozilla Berlin office. (Photo: Gemma Petrie)

Factors Influencing Workflows

While workflows are composed from atomic building blocks of tools, there is a great deal more that influences their construction and adoption among users.

Software Components

Software components are features of the operating system, the browser, and the specs of web technology that allow users to complete small atomic tasks. Some software components also constrain users into limited tasks or are obstacles to some workflows.

The basic building blocks of the browser are the features, tools, and preferences that allow users to complete tasks with the browser. Some examples include: Tabs, bookmarks, screenshots, authentication, and notifications.

Physical Components

Physical components are the devices and technology infrastructure that inform how users interact with software and the Internet. These components employ software but it is users’ physical interaction with them that makes these factors distinct. Some examples include: Access to the internet, network availability, and device form factors.

Psycho/Social/Cultural Factors

Psycho/Social/Cultural influences are contextual, social, and cognitive factors that affect users’ approaches to and decisions about their workflows.

Participants use memory to fill in gaps in their workflows where technology does not support persistence. For example, when comparison shopping, a user has multiple tabs open to compare prices; the user is using memory to keep in mind prices from the other tabs for the same item.

Participants exercised control over the role of technology in their lives either actively or passively. For example, some participant believed that they received too many notifications from apps and services, and often did not understand how to change these settings. This experience eroded their sense of control over their technology and forced these participants to develop alternate strategies for regaining control over these interruptions. For others, notifications were seen as a benefit. For example, one of our Leipzig participants used home automation tools and their associated notifications on his mobile devices to give him more control over his home environment.

Other examples of psycho/social/cultural factors we observed included: Work/personal divides, identity management, fashion trends in technology adoption, and privacy concerns.

Using the Workflows Model

When analyzing current user workflows, the parts of the model should be cues to examine how the workflow is constructed and what factors influence its construction. When building new features, it can be helpful to ask the following questions to determine viability:

Hamburg Train Station (Photo: Gemma Petrie)

Design Principles & Recommendations

Future Research Phases

The Firefox User Research team conducted additional phases of this research in Canada, the United States, Japan, and Vietnam. Check back for updates on our work.


¹ Pace, S. (2004). A grounded theory of the flow experiences of Web users. International journal of human-computer studies, 60(3), 327–363.

Firefox Workflow User Research in Germany was originally published in Firefox User Experience on Medium, where people are continuing the conversation by highlighting and responding to this story.

July 13, 2017 12:37 PM

June 22, 2017

Firefox UX: Let‘s tackle the same challenge again, and again.

Actually, let’s not!

The products we build get more design attention as our Firefox UX team has grown from about 15 to 45 people. Designers can now continue to focus on their product after the initial design is finished, instead of having to move to the next project. This is great as it helps us improve our products step by step. But this also leads to increasing efforts to keep this growing team in sync and able to timely answer all questions posed to us.

Scaling communication from small to big teams leads to massive effort for a few.

Especially for engineers and new designers it is often difficult to get timely answers to simple questions. Those answers are often in the original spec, which too often is hard to locate. Or worse, it may be in the mind of the designer, who may have left, or receives too many questions to respond timely.

In a survey we ran in early 2017, developers reported to feel they

  • spend too much time identifying the right specs to build from,
  • spend too much time waiting for feedback from designers, and
  • spend too much time mapping new designs to existing UI elements.

In the same survey designers reported to feel they

  • spend too much time identifying current UI to re-use in their designs, and
  • spend too much time re-building current UI to use in their designs.

All those repetitive tasks people feel they spend too much time on ultimately keep us from tackling newer and bigger challenges. ‒ So, actually, let‘s not spend our time on those.

Let’s help people spend time on what they love to do.

Shifting some communication to a central tool can reduce load on people and lower the barrier for entry.

Let’s build tools that help developers know what a given UI should look like, without them needing to wait for feedback from designers. And let’s use that system for designers to identify UI we already built, and to learn how they can re-use it.

We call this the Photon Design System,
and its first beta version is ready to be used:

We are happy to receive feedback and contributions on the current content of the system, as well as on what content to add next.

Photon Design System

Based on what we learned from people, we are building our design system to help people:

Currently the Photon Design System covers fundamental design elements like icons, colors, typography and copy-writing as well as our design principles and guidelines on how to design for scale. Defining those already helped designers better align across products and features, and developers have a definitive source to fall back to when a design does not specify a color, icon or other.


With all the design fundamentals in place we are starting to combine them into defined components that can easily be reused to create consistent Firefox UI across all platforms, from mobile to desktop, and from web-based to native. This will add value for people working on Firefox products, as well as help people working on extensions for Firefox.

If you are working on Firefox UI

We would love to learn from you what principles, patterns & components your team’s work touches, and what you feel is worth documenting for others to learn from, and use in their UI.

Share your principle/pattern/component with us!

And if you haven’t yet, ask yourself where you could use what’s already documented in the Photon Design System and help us find more and more synergies across our products to utilize.

If you are working on a Firefox extension

We would love to learn about where you would have wanted design support when building your extension, and when you had to spend more time on design then you intended to.

Share with us!

Let‘s tackle the same challenge again, and again. was originally published in Firefox User Experience on Medium, where people are continuing the conversation by highlighting and responding to this story.

June 22, 2017 07:12 PM

May 23, 2017

Firefox UX: Free Templates to Keep Your Design Sprint on Track

Like many organizations, Mozilla Firefox has been experimenting with the Google Ventures Design Sprint method as one way to quickly align teams and explore product ideas. Last fall I had the opportunity to facilitate a design sprint for our New Mobile Experiences team to explore new ways of connecting people to the mobile web. Our team had a productive week and you can read more about our experience in this post on the Sprint Stories website.

This year, Google I/O included a panel of Google “Sprint Masters” discussing how they use Design Sprints in their work: Using Design Sprints to Increase Cross-Functional Collaboration. A common theme during the discussion was the importance of detailed facilitator planning in advance of the Design Sprint.

What is the most important thing to do in preparing for a Sprint?
“The most important thing is planning, planning, and then more planning. I want to emphasize the fact that there are unknowns during a Design Sprint, so you have to even plan for those. And what that looks like is the agenda, how you want to pace the activities, and who you want in the room.” — Ratna Desai, Google UX Lead

When I was planning my first Design Sprint as a facilitator, I was grateful for the detailed daily outlines in the GV Library, as well as the Monday morning kickoff presentation. But, given the popularity of Design Sprints, I was surprised that I was unable to find (at the time at least) examples of daily presentations that I could repurpose to keep us on track. There is a a lot to cover in a 5 day Design Sprint. It’s a challenge to even remember what is coming next, let alone keep everything timely and orderly. I relied heavily on these Keynote slides to pace our activities and I hope that they can serve as a resource for other first time Design Sprint facilitators by cutting down on some of your planning time.

These slides closely follow the basic approach described in the Sprint book, but could be easily modified to suit your specific needs. They also include some presenter notes to help you describe each activity. Shout out to Unsplash for the amazing photos.

Design Sprint Daily Agenda Templates


Monday Keynote Slides (link)

10:00 — Introductions. Sprint overview. Monday overview.
10:15 — Set a long term goal. List sprint questions.
11:15 — Break
11:30 — Make a map
12:30 — Expert questions
1:00 — Lunch
2:00 — Ask the experts. Update the map. Make “How might we” notes.
4:00 — Break
4:15 — Organize the HMW notes. Vote on HMW notes.
4:35 — Pick a target


Tuesday Keynote Slides (link)

10:00 — Lightning demos
11:30 — Break
11:45 — Continue lightning demos
12:30 — Divide or swarm
1:00 — Lunch
2:00 — Four Step Sketch: Notes
2:30 — Four Step Sketch: Ideas
3:00 — Four Step Sketch: Crazy 8s
3:30 — Break
3:45 — Four Step Sketch: Solution sketch
4:45 — Recruitment criteria


Wednesday Keynote Slides (link)

10:00 — Sticky decisions: Showcase and vote
11:30 — Break
11:45 — Concept selection: Evaluate and vote
1:00 — Lunch
2:00 — Make a storyboard
3:30 — Break
3:45 — Complete storyboard
4:45 — Select participants


Thursday Keynote Slides (link)

10:00 — Pick the right tools. Divide and conquer.
10:10 — Prototype
11:30 — Break
11:45 — Prototype. Begin interview guide.
1:00 — Lunch
2:00 — Stitch it together. Test run video set-up
2:45 — Prototype demo
3:00 — Pilot interview
3:30 — Break
3:45 — Finish prototype. Update interview guide.
4:45 — Interview preparations.


Friday Keynote Slides (link)

9:00 — Interview #1
10:00 — Break
10:30 — Interview #2
11:30 — Early lunch
12:30 — Interview #3
1:30 — Break
2:00 — Interview #4
3:00 — Break
3:30 — Interview #5
4:30 — Debrief

Free Templates to Keep Your Design Sprint on Track was originally published in Firefox User Experience on Medium, where people are continuing the conversation by highlighting and responding to this story.

May 23, 2017 05:17 PM

May 03, 2017

Firefox UX: Things I learned working on Firefox Focus

We launched Focus as a free content blocker for Safari on iOS back in December 2015. The idea was to bring control back into users’ hands. We wanted to let them dictate how they wanted to spend their browsing data, even if they weren’t using Firefox.

About a year later, we wanted to give the product an update. We wanted to experiment more on Mobile. But how?

What if we could give mobile users an app that only allowed private browsing?
What would “success” or “failure” look like?
How were we going to do any of this?

Eventually, we released the update (and it’s on the App Store!). We learned a few things and now we’re working on Firefox Focus for Android.

Move together and move quickly

Our team was very small. So we needed to set expectations early — who’s responsible for what?

We tried to stay focused (heh) on a small set of well-defined goals. Everyone had a part to play. A clearly defined timeline helped us avoid scope creep too. It set the tone for our discussions and made it a lot easier to prioritize issues.

Slide from our presentation at our All Hands in Kona, HI (Source: Barbara Bermes)

We had weekly check-ins to make sure everyone was on the same page. All of our meetings were clearly directed and to the point. As things came up they would also be filed as GitHub issues so we always had a way to track our discussions.

It’s important to remember that getting 100% consensus is pretty much impossible. But “moving together” doesn’t necessarily mean everyone has to think the same. It’s natural to have doubts. Trust each other and try to move forward as a team. Define what success looks like together. Then go out, and gather some data.

Share early and often

Even if you aren’t finished, design comps/mock ups can really help provide a shared vision. Try to share them more! I’m guilty too sometimes. I know it can be hard. But I’ve always been glad that I did.

Where possible, we made all design changes “on device” using Buddybuild. This helped us arrive at decisions quicker, and with more confidence. It was great for design and engineering issues but it also kept the entire team in sync (especially useful when working across offices and timezones). Basically, it was our way of sharing early and often.

Erase button — “Good enough” initial designs

Then there was Slack . Lots of it. Our team was small, but distributed. Slack made it easy for anyone to give feedback, report/resolve GitHub issues, or even just give an encouraging 👍.

Sharing early might have pitfalls too. But it can get everyone involved and excited about the final product. Visual mock ups create a common language and helps avoid miscommunication later on. Share the vision, spread the workload. Insightful feedback can uncover interesting opportunities, but don’t let criticism stall you either.

Be flexible

Originally, Focus was a slightly different product. I didn’t work on the first version myself (that was mostly Darrin) but Brian (one of our engineers) did.

As designers, we should be opinionated but we also need to be flexible. Whatever decision we arrive at right now might not be ideal, but maybe that’s OK. Who knows, maybe sometimes we don’t have the right answer. Remember, it’s iterative!

Brian and I shared the same timezone but not the same office. So we spent a fair amount of time on Vidyo. Being on a video call over a long period of time can be really tiring. But it helped us hammer out the details quickly. When something didn’t make sense, we didn’t have to wait for the next weekly meeting to chat.

This is probably terrible of me, but I actually didn’t have a “full design spec” until towards the end of the project.

Screen sharing unfinished designs

Unfortunately, there isn’t a one-size-fits-all type of solution here. For us, Vidyo and Slack made the most sense but there were still drawbacks. Everyone’s different. Every team is different. Find a solution that works for you and your team. The key is to be flexible, to adapt.

There are always more opportunities to learn, and to grow. Within our products and ourselves as practitioners too. In the end, I really think it’s a constant process.

Firefox Focus on Android — Buddybuild #1420 on device

If you’re interested in contributing, here are the GitHub repos for Firefox Focus on iOS, and Android. Currently, we’re working towards the initial release of Firefox Focus on Android. Send any feedback, questions and comments you might have!

Things I learned working on Firefox Focus was originally published in Firefox User Experience on Medium, where people are continuing the conversation by highlighting and responding to this story.

May 03, 2017 07:17 PM

April 21, 2017

Firefox UX: Ratings and reviews on


My name is Philip Walmsley, and I am a Senior Visual Designer on the Firefox UX team. I am also one of the people tasked with making (or, “AMO”) a great place to list and find Firefox extensions and themes.

There are a lot of changes happening in the Firefox and Add-ons ecosystem this year (Quantum, Photon, Web Extensions, etc.), and one of them is a visual and functional redesign of AMO. This has been a long time coming! The internet has progressed in leaps and bounds since our little site was launched many years ago, and it’s time to give it some love. We’ve currently got a top-to-bottom redesign in the works, with the goal of making add-ons more accessible to more users.

I’m here to talk with you about one part of the add-ons experience: ratings and reviews. We have found a few issues with our existing approach:

So, as you can see, we’ve got quite a few issues here. So let’s simplify and tackle these one-by-one: Experience, Tags, Triage.

So many feels


Someone is not familiar with Lisa Hanawalt

The star rating has its place. It is very useful in systems where the rating you leave is relevant to you and you alone. Your music library, for example: you know why you rate one song two stars and another at four. It is a very personal but very arbitrary way of rating something. Unfortunately, this rating system doesn’t scale well when more than one person is reviewing the same thing: If I love something but rate it two stars because it lacks a particular feature, what does that mean to other users or the overall aggregated rating? It drags down the review of a great add-on, and as other users scan reviews and see 2-stars, they might leave and try to find something else. Not great.

What if instead of stars, we used emotions?

Some of you might have seen these in airports or restrooms. It is a straightforward and fast way for a group of people to indicate “Yep, this restroom is sparkling and well-stocked, great experience.” Or “Someone needs to get in here with a mop, PRONTO.” It changes throughout the day, and an attendant can address issues as they arise. Or, through regular maintenance, they can achieve a happy face rating all day.

What if we applied this method to add-ons? What if the first thing we asked a user once they had used an extension for a day or so was: “How are you enjoying this extension?” and presented them with three faces: Grinning, Meh, and Sad. At a very high level, this gives users and developers a clear, overall impression of how people feel about using this add-on (“90% grinning face for this extension? People must like it, let’s give it a try.”).

So! A user has contributed some useful rating data, which is awesome. At this point, they can leave the flow and continue on their merry way, or we can prompt them to quickly leave a few more bits of even MORE useful review data…


Not super helpful

Writing a review is hard. Let me rephrase that: Writing a good review is hard. It’s easy to fire off something saying “This add-on is just ok.” It’s hard to write a review explaining in detail why the add-on is “just ok.” Some (read: most) users don’t want to write a detailed review, for many reasons: time, interest, accessibility, etc. What if we provided a way for these users to give feedback in a quick and straightforward way? What if, instead of staring down a blank text field, we displayed a series of tags or descriptors based on the emotion rating the user just gave?

For example, I just clicked a smiling face to review an extension I’m enjoying. Right after that, a grid of tags with associated icons pops up. Words like “fast”, “stable”, “easy to use”, well-designed”, fun”, etc. I liked the speed of this extension, so I click “fast” and “stable” and submit my options. And success: I have submitted two more pieces of data that are useful to devs and users. Developers can find out what users like about their add-on, and users can see what other users are thinking before committing to downloading. We can pop up different tags based on the emotion selected: if a user taps Meh or Sad, we can pop up tags to find out why the user selected that initially. The result is actionable review data that can is translated across all languages spoken by our users! Pretty cool.


Finally, we reach triage. Once a user submits tag review data, we can present them with a few more options. If a user is happy with this extension and wants to contribute even more, we can present them with an opportunity to write a review, or share it with friends, or contact the developer personally to give them kudos. If a user selected Meh, we could suggest reading some developer-provided documentation, contacting support, or writing a review. If the user selected Sad, we’d show them developer or Mozilla support, extension documentation, file a bug/issue, or write a review. That way we can make sure a user gets the help they need, and we can avoid unnecessary poor reviews. All of these options will also be available on the add-on page as well, so a user always has access to these different actions. If a user leaves a review expressing frustration with an add-on, devs will be able to reply to the review in-line, so other users can see issues being addressed. Once a dev has responded, we will ask the user if this has solved their problem and if they’d like to update their review.

We’ve covered a lot here! Keep in mind that this is still in the early proposal stage and things will change. And that’s good; we want to change this for the better. Is there anything we’ve missed? Other ideas? What’s good about our current rating and review flow? What’s bad? We’d love constructive feedback from AMO users, extension developers, and theme artists.

Please visit this Discourse post to continue the discussion, and thanks for reading!

Philip (@pwalm)
Senior Visual Designer, Firefox UX

Ratings and reviews on was originally published in Firefox User Experience on Medium, where people are continuing the conversation by highlighting and responding to this story.

April 21, 2017 09:00 PM

February 04, 2017

Behind the Bikeshed: Rollie The Rapper, And Dollie The DogRollie started rapping many years ago, and since the beginning,...

Rollie The Rapper, And Dollie The Dog

Rollie started rapping many years ago, and since the beginning, Dollie was with him. In fact, when Rollie was born, Dollie was already a puppy. Dollie doesn’t talk, but with her expressions she can support Rollie before his concerts. Rollie already recorded many songs and videos, in which Dollie always appear. Dollie is also a theme in many of Rollie’s songs. She is the only dog Rollie ever had and besides of being close like siblings, Dollie is an inspiration for Rollie. Rollie wrote songs in which he talks of Dollie as his sister and he is going to sing it in his next concert. Now Rollie and Dollie doesn’t know if it’s a good idea to give milk to their dog.

February 04, 2017 11:45 AM


February 04, 2017 11:20 AM



February 04, 2017 11:20 AM

February 04, 2017 11:19 AM

January 05, 2017

Firefox UX: Project Prox?

Update on June 21st, 2017: We are no longer actively working on Prox. There are no plans for a post-beta release.

At our recent Mozilla All Hands in Kona, HI, we announced the first project by the New Mobile Experience Team— Project Prox.

A few of us on stage talking about the project to the rest of the org. (Photo credit: Bryan Bell)

This is our first experiment in the Context Graph space. It’s a peek into everything we talked about earlier in the year and what that experience might look like for our users.

So what the heck is it?

Right now, Project Prox is taking shape as a mobile-first application on iOS. Starting with your location, we look for interesting places and events near you. That’s where our focus is at the moment — the here and now.

Yes, there are also other parts to this story too. But we’ve decided that focusing on this part of the “Traveller’s” journey right now makes the most sense. This was also something we touched on during our Design Sprint. If you’d like to know more (and haven’t already), you can read more about that process here.

The Map from Day 1 of our first Design Sprint

But I don’t have an iPhone… why is it only on iOS?

Believe it or not, “only make this for iOS” wasn’t one of our goals. But with all our constraints, we felt that the iOS platform was the best place to start. We definitely want to expand to other platforms in the future. This came down to a matter of resourcing, time constraints, and the usual like.

It’s important to call out our goal here: to solve real user/people problems. We want to understand the problem space and provide user value through iterative research and design.

Is this something Mozilla should be doing?

When you think about Mozilla, it’s pretty much synonymous with Firefox. But surely that’s not the only way we can carry out our mission, is it?

Our mission is to ensure the Internet is a global public resource, open and accessible to all.

How do we define “the Internet”? It takes so many different forms nowadays. We might know what it looks like today, but what about the future? How will technology influence the way we interact with “the Internet” then?

Not too long ago, Mobile was the future. Now, the web platform itself is growing. Chrome’s Accelerated Mobile Pages, and Progressive Web Apps give us the ability to create new, better experiences for the mobile Web.

If we want to ensure that the mobile Web is also “open and accessible to all”, we need to grow the influence of the mobile Web too. We need to be open to new technology and consider all the different ways people are (and will be) accessing this information.

Ok, so what does Project Prox look like?

As soon as you open the app, we want to provide immediate value. Our goal is to enable easier decisions about what to do or where to go next. So, without even knowing what to start searching for, we want to leave you with a satisfying day.

Summary Card — Design mock of our Home view

We can leverage the Open Web by surfacing relevant information in bite-sized chunks and offering a quick and easy way to find out more. There should not be requirements (like your social network) when you’re trying to get the most from the web.

This should work regardless of whom you’re connected to, because your social network shouldn’t be a prerequisite for getting the most from the web.

For those looking for a less immediate perspective, we also included a “Map View”. This was actually not something we tested in our Sprint. But the intention here was to offer an alternative view for users to give them more context about their surroundings. The goal here was to give users a better sense of spatial awareness.

“Map” — Design mock of an alternate view

Although we never finished it in time for Kona, we still got a lot of helpful feedback that is going to help us iterate and test this more for the next version.

Last but not least, notifications! If you’re nearby an event, we’ll notify you so that you can decide if you’re interested or not. The nuances of notifications makes this helluva lot trickier. But more than anything, we want to be useful without being annoying.

Notifications — Received from Project Prox while I was in the Hilton

Keep in mind, all of this is still a work-in-progress. We’re going to continue iterating with the help of our User Research team until we have something we’re happy with.

What’s next?

All in all, it’s just too early to tell. Kona was our first announcement but we’ve yet to actually launch the product. But we do have a clearer picture of what success might look like for us.

We’re calling this a “V1” — so there’s lots of work to be done still. We’re going to address some of the feedback and bring the product to a level we’re comfortable with calling an MVP before releasing to a larger population. And obviously, it works better in some cities versus others.

We need to get more data and gather more feedback. Improving the experience and releasing the updated product in a larger, denser city will be our next challenge. What we learn there will help us determine the appropriate next steps.

If you’re interested in giving feedback, please reach out!

Project Prox? was originally published in Firefox User Experience on Medium, where people are continuing the conversation by highlighting and responding to this story.

January 05, 2017 09:17 PM