cancel
Showing results for 
Search instead for 
Did you mean: 

Template:addmobiledevice

  1. Tap the Menu button (either below the screen on some devices or at the top-right corner of the browser) , choose Settings (you may need to tap More first) and, finally, Sync.
  2. Tap the "Advanced setup..." link.
    sync_recovery3
  3. Next, enter your Account Name (email address), Password, Recovery Key and tap Connect.
    sync_recovery4
Customize this article

Firefox

Firefox for Android

Firefox for iOS

Firefox OS

Thunderbird

Version History
Revision #:
3 of 3
Last update:
3 weeks ago
Updated by:
 
Tags (1)
Comments

I have a couple thoughts about the latest revision for the native UI.

  • Important: We should explain how to get to the sync setup. People may not know how to get to that sync button. If you've navigated away from the start page or closed that tab there is not a clear way back. Instead, it might be better to point to Menu > More > Settings > Sync. That's always available.
  • Minor: I don't think we need to blur out the jpake code. It's only active for a few minutes so there is no chance of someone connecting to the displayed sync account. It's also probably less distracting that we show the screen as is (instead of the user wondering why it's blurred out).
  • Minor: Images like this can also work side-by-side to save some scrolling in an already long article. Just list the images in line, e.g. [[Image:Image1]]&nbsp[[Image:Image2]]
  • Minor: Red callouts might be better (and consistent with the rest of the article) than green. The green ones kind of look like they are part of the android interface.

Michelle and I had a conversation about the first point last Friday. The conclusion is that HW buttons are a PITA and the main screen always shows the Sync button until it's configured so it's a much more clear and easy way of triggering the process.

While that's true, I do see now that we may want to add an initial step to say "Launch Firefox in your mobile device".

I leave the other comments to Michelle who has the screenshots.

Related to Scoobi's edit...why shouldn't we use "for not m11"?? Some context in the edit will be beneficial. "For not" simplifies the syntax a lot and we should use it more often.

Best, Ibai

Ibai said

Related to Scoobi's edit...why shouldn't we use "for not m11"?? Some context in the edit will be beneficial. "For not" simplifies the syntax a lot and we should use it more often.

Originally {for not m11} would have meant for less than fx11 and greater than fx11 but this was changed late last year to just mean less than. So we can use "not" now, which is much easier.

Hi,

Thanks for this review feedback.

I actually think that first button is a bit more confusing for people new to the web, so that is part of the reason I'm documenting it instead of the Sync menu item that is available via More -> Settings. This has already come up in the forum in a different context and I discussed it with Madhava yesterday, so I'd like to keep the revision with the button on the about:home page as the reference.

I'm also using the green labels on purpose to match the colors of the buttons when selected in the interface, but I'm happy to rework them with red later if this way doesn't work.

-Michelle

mluna said

I actually think that first button is a bit more confusing for people new to the web, so that is part of the reason I'm documenting it instead of the Sync menu item that is available via More -> Settings.

That's an indication that the product needs to be fixed; not documented (We should invite Madhava to this discussion). The fact is that the about:home page will not always be visible. In fact, it will often not be visible. Typical use case - I open Firefox and click on one of my top sites. The button is now gone. If I'm smart and I happen to want to set up sync at this point I might now that I can navigate back once in my history to get the button. But go to a few more sites or open another tab and there is no obvious way to get it back. So if we want to document that method you have to explain that it's only available from the start page and the way to get to the start page if you are not there at the moment is to use Menu > More > Quit and then restart Firefox. I believe that's a more complicated workflow, prone to cause more problems.

Using the Menu > More > Settings > Sync approach could even help with the big button use case. For example, if I click the button and then click the "show me how" link I'll be taken to a support article. If I'm a new Firefox user I may not understand that a new tab has opened and it may not be obvious how to get back to the big button. But Menu > More > Settings > Sync will always get you back there.

When I talked to Ibai, he brought up other concerns, like the menu button symbol on some phones and I addressed that in my revision by including a picture of that version of the button (we do this for things like the "bookmarks" button on desktop). Long term, we may need to add ICS support to the wiki. Another concern he had was the hardware menu button being confusing in general but if that's the case we're sunk because you need it to do many things (find your version number, change character encoding, plugin settings, clear history, clear private data, set dnt, password settings, cookie settings, enable telemetry and set a master password). After having that conversation, Ibai agreed that it was probably best to use Menu > More > Settings > Sync.

One more reason not to use the big button - the day they decide to use that real estate on about:home for something else, we have to change all of our documentation. Of course that's always a risk but if about:home in fennec is at all like about:home in desktop it's probably a bigger risk than changing the menu hierarchy (i.e. it won't go though 18 weeks of testing).

Verdi said

Typical use case - I open Firefox and click on one of my top sites. The button is now gone. If I'm smart and I happen to want to set up sync at this point I might now that I can navigate back once in my history to get the button. But go to a few more sites or open another tab and there is no obvious way to get it back.

IMHO, this usecase is far from "typical". I don't see a user having an "a-ha" moment in the middle of their navigation and decide to set-up Sync, go to SUMO to learn how to do it and start the process.

The typical usecase, again IMHO, is to see the big button in front, click on it..start the process...get confused with the code, go to Google to search for info or find the right link to end up in SUMO to get an explanation.

Verdi said

Using the Menu > More > Settings > Sync approach could even help with the big button use case. For example, if I click the button and then click the "show me how" link I'll be taken to a support article. If I'm a new Firefox user I may not understand that a new tab has opened and it may not be obvious how to get back to the big button. But Menu > More > Settings > Sync will always get you back there.

I mentioned that in our conversation and I feel that this is actually confusing. A user who is already in the process through the "big button" and suddenly is explained that to use Firefox Sync you need to first go to settings->sync can get somehow confused.

Verdi said

One more reason not to use the big button - the day they decide to use that real estate on about:home for something else, we have to change all of our documentation. Of course that's always a risk but if about:home in fennec is at all like about:home in desktop it's probably a bigger risk than changing the menu hierarchy (i.e. it won't go though 18 weeks of testing).

In Firefox 13 chances are that we will streamline the login by using BrowserID. So any solution we take today is going to be live for 2 (or 3) releases. I don't see this as a powerful argument to be honest.

That said, I don't think that arguments for one or the other options are that dramatic or critical. So if any of you have strong feelings about one or the other, go ahead.

Ibai said

IMHO, this usecase is far from "typical". I don't see a user having an "a-ha" moment in the middle of their navigation and decide to set-up Sync, go to SUMO to learn how to do it and start the process. The typical usecase, again IMHO, is to see the big button in front, click on it..start the process...get confused with the code, go to Google to search for info or find the right link to end up in SUMO to get an explanation.

Ibai, I don't understand - we talked for like 20 minutes about this. If you don't click that big button when you first open the browser and instead, actually use the browser (if that's not "typical" it's at least common) you won't necessarily know how to get back to that big button. The current instructions don't explain how to get to the screen with the big button. When I look at my phone right now I don't see it. How do I get there? I can ALWAYS get there with Menu > More > Settings > Sync.

Again, I'll say if that big button is confusing - it's a product problem not a documentation problem. We should collect forum threads, file a bug, talk to Madhava, bring this up in meetings, etc. If there still isn't any will to do anything about it then we document it like an issue. "What the hell is this big sync button?" "Do I need Sync to use Firefox?" or whatever people are saying.


Ibai said

Verdi said
One more reason not to use the big button - the day they decide to use that real estate on about:home for something else, we have to change all of our documentation. Of course that's always a risk but if about:home in fennec is at all like about:home in desktop it's probably a bigger risk than changing the menu hierarchy (i.e. it won't go though 18 weeks of testing).

In Firefox 13 chances are that we will streamline the login by using BrowserID. So any solution we take today is going to be live for 2 (or 3) releases. I don't see this as a powerful argument to be honest.

Sure this may not be the strongest argument (it was an afterthought) but even when we use browser ID, the place to access sync settings will still be Menu > More > Settings > Sync.

Hi,

Thanks again for this feedback, much appreciated (however embarrassing).

We have passed string freeze for nativeUI and I have discussed the button with Madhava, so the documentation draft I created is based on all the available information.

I have added a note to a new revision to let people know they can get to the Sync set up through the Settings with a pointer to the full set of screen shots in the getting started article and I qualified the original step with the Firefox Start page, which is how it shows up in the bookmarks.

-Michelle

As far as i know the "Pair a device" for Sync is not being used anymore. So this article should be updated if im correct, as to not confuse the users when they try to learn about Sync.

I tested this in emulator with Android 5 and Firefox 34.0. and the link in step 2 does not exists.