Closed Bug 1064926 Opened 5 years ago Closed 5 years ago

Feature other recommended add-ons in "Firefox Privacy Coach" add-on

Categories

(Firefox for Android :: General, defect)

35 Branch
All
Android
defect
Not set

Tracking

()

RESOLVED FIXED
Tracking Status
fennec + ---

People

(Reporter: krudnitski, Assigned: tecgirl)

References

Details

The intent of this home panel is to bundle it in with the 'Firefox Confidential' add-on. However, it can also be used as a standalone if we wish to promote add-ons we feel represent privacy & security really well as a secondary consideration.

The idea is to display recommended add-ons (and in this case, applicable to the 'Firefox Confidential' initiative) in a visually appealing way and having them link to their AMO landing page for easy installation.
tracking-fennec: ? → 33+
CC Robin, since she has been putting some thoughts on this.
Could we have installation occur from a CTA on the Add-on panel?
The panel items correspond to URLs, and we open those URLs when they are clicked. We can probably have an add-on install happen if we specify a URL directly to the APK, but we'll probably also open a new tab, which might not be the nicest experience.
Thinking about this bug a bit more, I don't know if this really makes sense to do. Adding a home panel that just promotes some more add-ons feels a bit invasive. Home panels are designed to contain stuff that you want to come back to, but I don't envision users wanting to re-visit a panel of promoted add-ons. I also worry that they might be surprised to find this add-on added a new panel, since it feels a bit out of the scope of a privacy-focused add-on.

Robin and I were talking about this earlier, and perhaps a better solution would be to show users a page about these additional promoted add-ons after they install the Firefox Confidential add-on.
(In reply to :Margaret Leibovic from comment #4)
> Thinking about this bug a bit more, I don't know if this really makes sense
> to do. Adding a home panel that just promotes some more add-ons feels a bit
> invasive. Home panels are designed to contain stuff that you want to come
> back to, but I don't envision users wanting to re-visit a panel of promoted
> add-ons. I also worry that they might be surprised to find this add-on added
> a new panel, since it feels a bit out of the scope of a privacy-focused
> add-on.
> 
> Robin and I were talking about this earlier, and perhaps a better solution
> would be to show users a page about these additional promoted add-ons after
> they install the Firefox Confidential add-on.

Yeah, this makes sense to me. Especially when I think about the new tab popping up and revisiting aspect that you bring up.

A mobile friendly website that stems from a "learn more" type of link (or something) seems like a good enough solution since users could then share that site relatively easily at their own leisure. Not to mention, users wouldn't need Firefox to discover this page (marketing points bonus!)
tracking-fennec: 33+ → +
Updating the summary to here to more generally describe what we're trying to achieve.

As I've mentioned before, I don't think a home panel is actually a good solution here. I like the idea of opening a page after the add-on is installed. The simplest way to do this would be to just bundle an HTML page in the add-on, so that we don't need something on a server somewhere. Something like "Welcome to the Privacy Coach add-on!", which can contain some more info about the add-on, and perhaps a link to a collection of featured add-ons on AMO.

UX folks, what do you think of this? My mantra here is "keep it simple".
Summary: Create a home panel that features recommended add-ons → Features other recommended add-ons in "Firefox Privacy Coach" add-on
I second Margaret's notion (again). Adding a panel is counter to the experience we're trying to achieve with a privacy-centered add-on. I am very much for keeping it simple. Let's go with the landing page.
I like where this is heading - this is great. 

Robin, last week we also talked about the following idea, so putting it in here as well for logging purposes. In the landing page, I'd like to take the opportunity to inform users about the prefs we've switched off, WHY as well as any trade-offs in doing so, and how to switch them back on. Of course, we can link out to sumo articles detailing anything above and beyond some simple messages, but I'd like the user to be educated as possible about what this add-on actually does (ie a quick way to lock down your browser although some trade-offs in browsing the web may occur as a result).

Could this be part of your design please?
I talked to Robin about this, and she said she would be able to create an HTML page for this.

I just updated the add-on to open an HTML welcome page when the add-on is installed, and the page for that is here:
https://github.com/leibovic/privacy-coach/blob/master/content/welcome.xhtml

Robin, if you're comfortable, you can make a PR to my github repo to fill in the content/style for this HTML page. I created a CSS file, as well as a DTD file where strings should live for localization.

I can also do this, but if you're working on the page itself, it might be easiest to just do it right in the add-on :)
Assignee: nobody → randersen
Summary: Features other recommended add-ons in "Firefox Privacy Coach" add-on → Feature other recommended add-ons in "Firefox Privacy Coach" add-on
I'm still working on the content, and could use some assistance filling it in.
http://people.mozilla.org/~randersen/privacy-coach/

When the actual content is there I can PR your repo with the html page, 3 css files, and the icon (lock on a whistle - PRIVACY COACH, *booom!*).
Flags: needinfo?(margaret.leibovic)
Flags: needinfo?(krudnitski)
Arcadio - can you also please provide some assistance to the content?
Flags: needinfo?(krudnitski) → needinfo?(alainez)
(In reply to Robin Andersen [:tecgirl] from comment #10)
> I'm still working on the content, and could use some assistance filling it
> in.
> http://people.mozilla.org/~randersen/privacy-coach/
> 
> When the actual content is there I can PR your repo with the html page, 3
> css files, and the icon (lock on a whistle - PRIVACY COACH, *booom!*).

I think that looks good to me so far. Let me know if you need help making a PR when you get the final strings!

One question: do we want to recommend specific add-ons in this page? We could do that, or alternately we could link to the "Security & Privacy" category on AMO. I like that idea because it teaches users they can browse categories on AMO, and it's a kick in the butt to make sure the featured add-ons there are up to date.

Another note: As we talked about in bug 1064998, I don't think we'll be able to build anything into the add-on to show that your searches aren't going over HTTP. So this blurb should be updated to reflect whatever we're actually going to do in that bug.
Flags: needinfo?(margaret.leibovic)
I'm going to mark this bug as fixed, and file a follow-up bug for finalizing the copy in the welcome page. We can also make that bug about coming up with copy for the listing on AMO.
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → FIXED
Closing this NI
Flags: needinfo?(alainez)
You need to log in before you can comment on or make changes to this bug.