Decommissioning the F1 add-on

[James Burke]

I have started to update the Mozilla F1 website[1] and share panel to
state that the sharing experiment has transformed to a new add-on, and
point people to the new Firefox Share add-on[2].

Why? Since the active share development work is happening in the new
add-on's share approach, not the old F1 approach. Only the newer
approach will be getting updates.

How? Since these changes are on the web side, they do not require
anyone to update their F1 add-on to get the change. Given that the
panel content is cached around first load, after these changes are
rolled out, it still may be a few days before everyone starts to see
the new panel UI.

The end result: the user will not be able to use F1 to share once this
updated is deployed and their browser fetches the new panel content.

This work is only in dev right now, it is not deployed yet.

Here is what I have right now for the updated home page:

http://tagneto.org/temp/f1/homepage.png

Here is what the panel looks like now:

http://tagneto.org/temp/f1/panel.png

The buttons in those snapshots go to the Add-ons page for the Firefox
Share add-on[2].

Any adjustments to the wording needed? Does it look OK?

I would like to wrap up any changes and figure out the deployment
strategy in around a week's time.

[1] http://f1.mozillamessaging.com/
[2] https://addons.mozilla.org/en-US/firefox/addon/firefox-share-alpha/

James

[David Ascher]

Thanks for leading this charge, James.

I think the homepage needs a bit more drastic a redesign -- the layout
still looks at first glance like the old one, and text changes alone
won't get noticed.

In the interest of simplicity I'd remove the panel UI from the home page.

I also think we need to do a couple of things before we pull the trigger:

- explain what the new add-on is, how it's better (in particular that
we've made progress on figuring out long-tail support, and that it's
actively moving towards a firefox landing), and how it's worse (in
particular, no multiple-accounts-per-service, and no posting-to-pages IIRC).

- make sure that the newer add-on is "ready for users". I'm seeing some
visual display bugs that I suspect we want to fix before migrating a lot
of users to it.

--david

[James Burke]

On Mon, Feb 27, 2012 at 1:53 PM, David Ascher <das...@mozilla.com> wrote:
> In the interest of simplicity I'd remove the panel UI from the home page.
>
> I also think we need to do a couple of things before we pull the trigger:
>
>  - explain what the new add-on is, how it's better (in particular that we've
> made progress on figuring out long-tail support, and that it's actively
> moving towards a firefox landing), and how it's worse (in particular, no
> multiple-accounts-per-service, and no posting-to-pages IIRC).

Here is an attempt to integrate that feedback:

Home Page:
http://tagneto.org/temp/f1/homepage2.png

Panel:
http://tagneto.org/temp/f1/panel2.png

> - make sure that the newer add-on is "ready for users".  I'm seeing some
> visual display bugs that I suspect we want to fix before migrating a lot of
> users to it.

OK, I'll wait to pursue an update to the site until Shane or you give
me the word.

James

[Shane Caraveo]

The thing that is in the back of my head...even the Firefox Share addon
on AMO is essentially end-of-lifed as we work on the revamped share to
be integrated into Firefox. I'm not sure how to message that,
considering we'll have to do the same thing again in the near future.
Shane

[David Ascher]

On Mon Mar 5 14:52:49 2012, Shane Caraveo wrote:
> The thing that is in the back of my head...even the Firefox Share
> addon on AMO is essentially end-of-lifed as we work on the revamped
> share to be integrated into Firefox. I'm not sure how to message that,
> considering we'll have to do the same thing again in the near future.

Let's worry about that later? Best case scenario we still have 18
weeks to provide coverage for, no?