A quick update on Firefox for Android Tablets

Posted by ibarlow

1

We’re rapidly approaching the end of our blocker list on the all-new Firefox on Android Phones. Up next is a slew of enhancements to Firefox on Android Tablets, including:

  • Improved performance with a full rewrite of the browser, moving from the current XUL-based UI to the same Java-based UI that our upcoming phone browser uses.
  • An all-new theme that matches that of the new Firefox on phones, and builds on our goal of unifying the look and feel of Firefox across all our supported platforms. You can read more about this in Madhava’s recent blog post on the state of Firefox UX, and Patryk’s post on Firefox Visual Design.
  • A number of new features, including Search Suggest in the Awesomebar, a Reader Mode, and an improved Start Page.

Related Flickr Sets: http://bit.ly/IJg6Cs and http://bit.ly/IyogBc

Below is a list of features in progress, and their associated bugs. Many of these are based on designs for 10” tablets, but parallel work will be happening to update the UI on phones and 7” tablets, where appropriate.


Title Bar
[Bug 739355]

  • URL Bar with Title
  • Back button
  • Progress indicator (spinner + bar)
  • Conditional forward button
  • SSL / EV indicators
  • Addons indicators
  • Bookmark
  • Refresh
  • Stop
  • Overflow Menu


Awesomebar


Tabs Menu
[Bug 739407]

Remote Tabs [Bug 739411]

Overflow menu [Bug 739412]

Site ID Menu  [Bug 739356]

Bookmark management  [Bug 739359]

Doorhanger Notifications

In-content UI

Reader Mode [Bug 696921]

Reading List

Share

Site Settings

Settings (Native Settings UI)

Error Pages

Addons Manager

Access to Add-ons in browser UI

  • Menu
  • Widgets in menu or header on large tablets
  • Full page in-content UI

Gesture Support

  • one-fingered dragging to scroll pages
  • double tap to zoom / unzoom
  • pinch to zoom
  • long press links for context menu (open in new tab, etc)
  • long press text to activate text selection mode
  • swipe from left edge of screen to open tabs menu
  • two-fingered side to side dragging for back / forward controls
  • Explore pulling down on header to reveal tabs tray (on phones)
  • Explore pulling down on content to reveal home screen / awesomebar

Update on Firefox 13′s Home and New Tab Redesign

Posted by Jennifer Morrow

13

Two Firefox features getting a redesign in Firefox 13 (currently in beta) are the Home Tab and New Tab. Home Tab can be viewed by clicking house icon in Firefox or by typing “about:home” into your URL bar. New Tab appears when you click the “+” at the end of your tab strip.

Firefox 13 New Tab Page

Firefox 13 New Tab Page

Firefox 13 Home Tab Page (launch targets emphasized)

Firefox 13 Home Tab Page (launch targets emphasized)

Firefox’s Home Tab and New Tab have, until now, had fairly basic pages. In Firefox 12, Home Tab had a large search bar, a “snippet” which Mozilla uses to display messages to users, and little else. The main reason the search bar is on Home Tab is because many users click the Home button to initiate a search, either unaware of the toolbar search box or preferring not to use it. The snippet allows Mozilla to give a message to users, such as last October when it asked users in the United States to contact their representatives when the anti-internet-freedom bill SOPA was being heard in the House of Representatives. Such messages can be important while not being urgent enough to disrupt users with a notification.

New Tab, for most of Firefox’s history, has been completely blank. This was done deliberately to offer users a clean, fresh “sheet” to begin a new browsing task. However, a blank tab may not be distracting, but it’s also not useful.

Surely, we thought, we can present a more helpful design than a blank page! Using Mozilla Test Pilot, we began to research how Firefox users use New Tabs. What we learned is that each day, the average Firefox user creates 11 New Tabs, loads 7 pages from a New Tab, and visits two unique domains from a New Tab. The average New Tab loads two pages before the user closes or leaves it.

What this tells us is that users create many New Tabs, but they’re very likely from those to return to a limited number of their most-visited websites. So, we began to experiment with giving users quick access on New Tab to the websites they visit most frequently.

What you’ll see on the New Tab page of Firefox 13 are your most-visited sites displayed with large thumbnails, reducing the time it takes to type or navigate to these pages. This data comes directly from your browsing history: it’s the same information that helps Firefox’s Awesome Bar give suggestions when you type. Or, if you want to go somewhere new, the URL bar is still targeted when you type on a New Tab page. If you want to hide your top sites – permanently or temporarily – a grid icon in the top right wipes the new tab screen to blank.

Mozilla Home is getting a redesign, too! While still keeping the prominent search bar and snippet, the graphic style is softer, the text is more readable, and launch targets at the bottom allow you to quickly access areas such as Bookmarks, Applications, and previous Firefox sessions.

Both Home and New Tab are being improved as part of our longterm vision of making Firefox more powerful, engaging, and beautiful. Over the next few releases, more design improvements will be made towards this goal. For now, please try out Firefox’s new Home and New Tab pages in Firefox 13 Beta and tell us that you think!

Why You Should Be Excited About Test Pilot 2.

Posted by glind

0

Test Pilot 2 is coming soon.  In version 1, Jono had to discover what was possible.  Now that we know that everything is possible, we want to help Test Pilot instrument everything.   Here are some of our guiding principles.

easy to write studies

Here is an example study:

const observer = require("observer-service");
observer.notify("myspecialstudy",{my:'data'});

Studies message the global Observer service with observations.  Test Pilot listens.  The rest is details.

Some details:  Test Pilot 2 is a mechanism for installing addons, deciding which topics to observe, linking to external surveys, cleaning up the mess, and giving good UI and UX that ties it all together.

we meet you where you are.

No matter how you write your feature, we have you covered!  Our preferred way of running experiments is by installing Addon-SDK (née Jetpack) addons.  Of course,  your feature is so radical that it can’t be done as an addon, and only a separate binary build / Firefox branch can contain the magic.  We planned for that.

simple surveys

Linking to an external survey url is easy.  You decide who sees it, based on channel, locale, operating system and more.

the privacy you’re used to

Test Pilot remains transparent about exactly what data it collects.  We honor the contract we have with users that by sharing data about their habits, they should get something of value.  They are in charge of their data.

easier studies = more studies (and faster turnaround)

It should be cheap to do experiments.  It is always the right time to be bold.

Every feature of the browser should go in front of real users for testing.  During initial research, this might be a simple as doing hallway testing.  As a feature grows, it requires more.  Test Pilot can offer you large-scale quantitative data on “in the wild” populations, on both existing behaviours, and experimental changes to the browser interface.  Take your experiments public with Test Pilot, and find how users really react.

How can I sign up?

Need a study done?  Write to the User Research team at ( ur-team AT mozilla.com ), or stop by #ur .

Developers:  hack on the code at https://github.com/gregglind/testpilot2/.

You can join in studies today by installing Test Pilot.

Visual Reboot of Firefox Mobile for Android

Posted by Patryk Adamczyk

13

Design is the Differentiator.

Firefox is a premium application with a strong and distinct brand. With a recent strong wave of competitive browsers, all with similar features; design and product identity has become the differentiator. When high performance and stability are expected, a smart user experience and an emotional connection to the brand is what drives users to use the product.

Firefox design is focused on a swift, direct mobile experience. Magazine like aesthetic, less emphasis on decoration with greater focus on content and the tools to ease its access. Forms are rendered with a fine balance of organic and geometric shapes to further echo the Firefox brand messaging. Controls and layout are minimal, with emphasis on function. The aesthetic design promotes interaction with clear, direct iconography, rendered with friendly and efficient forms.

The visual design has been carefully crafted to communicate Firefox’s character subtly through a tasteful aesthetic which accents the native design language. However there are areas of the Firefox aesthetic which were designed to further maintain a unique feel.

 New Start Page & Interface Design

  • Colourful layout with large thumbnails (if available).
  • Unified curved tab design.
  • Awesome Screen data integrated into the start page.

 

Visual Design Differentiators.

 

Tab Shape

Fluid and organic, unique to Firefox.

 

Awesome Screen

Unique to the Firefox experience.

 

Orange Focus Highlight

  • Speaks strongly to the Firefox brand.
  • Future plan includes the transitioning of all native (blue in Ice Cream Sandwich) highlights to our Firefox orange.

 

Consistency and Polish.

Through iteration and testing we have refined the interaction patterns for both phone and tablet use. Resulting in a unified Firefox experience across the Firefox landscape while being conscious of user specific needs on each platform and form factor.

The visual design first seen in the refresh of Firefox Mobile on Android will evolve into the unified style spanning across all devices (phones, tablets, tablet PCs) and on many platforms. Resulting in a purpose-built UI, optimized for portrait and landscape orientations on phones and tablets; while still maintaining a quality and consistent user experience.

 

Visual Elements.

Layering

As an advanced web browser, Firefox gives the user various tools and options. These options are hidden behind the web content, invoked with a gesture (swipe). The rendering of these panels is darker appearing as if they are deeper in the Z axis, beneath the core content. The transitions simulate the movement of the view port to reveal more content.

 

Colour

On Android often instances of colour inconsistency exist between the flavours of Android. On many devices you’ll see at least 2 colours used for focus states. On Android 4.x devices you’ll see blue and orange (for legacy apps) while on skinned devices running Android 2.3.X, the user will experience the manufacturer’s brand colour and the native Gingerbread orange.

Aim is for a cohesive user experience on Firefox properties, leading with design that is unique to Firefox and doesn’t depend on manufacturer or Google Android skinning while maintaining familiar interaction elements.

A desaturated blue (silver) acts great as a field colour both for the Firefox logo and various text / media content. Use of a saturated blue over a gray allows for a friendlier experience. The hint of blue in the grays acts as a great high contrast complementary colour when used with the orange highlight.

Texture

Texture / noise has been introduced into the backgrounds for both greater aesthetic interest and reducing banding found in subtle gradients on some lower colour depth screens.

 

Hints at Interaction.

In a touch interface it is expected that everything can be interacted with, but good user experience should guide interaction and not promote trial and error pecking. With subtle lighting effects, touch elements will appear closer to the user on the Z axis and appear more pressable than other items. The reverse effect is applied to input fields, subtly carved into the chrome, hinting that the form can be filled; with text in this case.

Size

Size and spacing is based on physical measurements to optimize for scalability between various form factors. Due to larger real estate tablet can afford for larger touch targets and more easily accessible actions.

Phones

Bar Height: 7 mm
Input Field Height: 5 mm
Button Widths: 5 mm
Input Field Text Height: 7 pt

Tablets

Bar Height: 9 mm
Input Field Height: 7 mm
Button Widths: 9 mm
Input Field Text Height: 9 pt

Forms

All shapes and icons are rendered to have inviting feel to further engage the user:

  • Forms are rendered with soft edges
  • Corners possess a small radius
  • Objects possess realistic shading

Pressable Items

Any item that manipulates chrome should have some 3D styling, rising above the background. This can be accomplished with a drop shadow and / or bevel.

Input Fields

Any item that acts like an input field should be inset in the surface that it is set upon. The design’s aim is to invite the user to interact with the control but not feel it will work like a button since it doesn’t appear that it can be pressed down.

Lessons Learned from Researching in China, Japan and India

Posted by Diane Loviglio

0

Carissa Carter, a design researcher, formerly from Herman Miller,  shares what she learned from doing research in Asia for a full year.

Her top 5 lessons learned were:
1) Understand the enhanced impact of recent history.
2) Find the momentum of the population.
3) Tap into self-perceptions.
4) Use images as language.
5) Know what you’re up against and leverage it.

We also talked about best practices around incentives, translators and scheduling.  In China for example, if you interviewed a CFO and a designer at the same company, and you spent an hour with each and each interview was extremely valuable, you would give the CFO a bigger and better incentive.  And actually the incentive is viewed more of as a gift – a token of your appreciation – not payment for your time.  Physical size matters too, it’s not just the cost of the gift, it has to be bigger in size.  They gave planners with the company logo and shinny gold zippers and edges to the CFOs and a shiny jump drive to the lower status participants.

As for translators, she cautioned us to spend time picking the right one, since that person is channeling your questions to the participants.  She tried using a real time translator, but that didn’t prove to be useful, nor does a translators that asks a question and then tells you the answer afterwards in front of the participant, because that is too slow.  For participants who spoke English, she was the primary interviewer, but the local researcher still comes along so that afterwards they can shed light on why the participant made that face as he answered your question or why his answer was actually even more significant than you originally thought.

Scheduling is easy when you know your way or when you are driving yourself around, but in India for example, the traffic is so congested, that something that is 10 minutes away on a map, maybe actually take an hour to get to, so work with your  local researcher for scheduling too.

There are so many more details in her talk, it’s definitely worth watching her talk and reading her slides.  Thanks, Carissa!