Closed Bug 880494 Opened 11 years ago Closed 6 years ago

A mobile-friendly privacy policy page

Categories

(Firefox Health Report Graveyard :: Web: Health Report, defect, P5)

Product:
Firefox Health Report Graveyard
Component:
Web: Health Report
Platform:
All
Android
Type:
defect

Tracking

(Not tracked)

Status:
RESOLVED INCOMPLETE

People

(Reporter: abc, Unassigned)

References

Details

(Whiteboard: [measurement:client]) 

We need a mobile-friendly privacy page that the Fennec Health Report can link to.
This might be better in the SUMO component, but web will do for now.
Component: Client: Android → Web: Health Report
OS: Mac OS X → Android
Hardware: x86 → All
Blocks: 880534
No longer blocks: 880534
Hi Arun and Richard, below is my attempt at summarizing the problem and proposing a few solutions.


PROBLEM STATEMENT
=================

As far as I’m aware, there are three different components to this bug:
1. Firefox Health Report page, in-browser
2. SUMO article about FHR, hosted on sumo.mozilla.org
3. Privacy Policy page, hosted on mozilla.org

These three pages need to have:
1. Mobile friendliness: preferably responsive?
2. Visual design coherence: every page should feel like it belongs together
3. Seamless interaction: page structures and elements should be consistent

Currently, what we have is something like what’s outlined below.


DESKTOP USER FLOW
=================

 FHR    --->    SUMO article    --->    Privacy policy page
(good)             (good)                 (inconsistent)

On desktop, the FHR can be designed to look a little more like Sandstone. SUMO already looks like Sandstone, so no problem there. Finally, the we’ll need to update the privacy policy page to Sandstone.

It’s not complex: just a case of extending the existing design.


MOBILE USER FLOW
================

  FHR      --->           SUMO article        --->    Privacy policy page
(design)           (has non-Sandstone style)          (not designed yet)

On mobile, the situation is complex, one of the cause being the fact that SUMO mobile UX was designed to function like a Firefox OS app rather than a Sandstone-style website.


POSSIBLE SOLUTIONS
==================

There are two possible paths to take on mobile:

1. Design FHR so it functions like a responsive Sandstone-style page. SUMO must follow this convention, at least for the FHR article page. How do we do this?

2. Design FHR so it functions more like a Firefox OS app. SUMO doesn’t need to be redesigned, but FHR might not match the style of the rest of the browser chrome


ALTERNATIVE SOLUTION
====================

Move or mirror the FHR article page out of SUMO and host it on mozilla.org. This way, the page style automatically becomes responsive Sandstone. The concern here is article maintenance


WHAT WILL HAPPEN TO THE PRIVACY POLICY PAGE
===========================================

The privacy policy page will need to be redesigned to follow whichever path we choose to take. We’ll need to file a bug for this.
> MOBILE USER FLOW

For clarity: I'm only concerned at this point with the mobile experience.


>   FHR      --->           SUMO article        --->    Privacy policy page
> (design)           (has non-Sandstone style)          (not designed yet)

We explicitly don't wish to reach the privacy policy via SUMO, at least as far as I understand it.

"Learn more" and the privacy policy should be static content; we don't wish them to be modified without privacy and legal review. They can link to SUMO, as can the rest of the app:

FHR  ---->  Privacy policy and FHR description
                               |
                               V
     -------------->  SUMO FAQ and such


> POSSIBLE SOLUTIONS
> ==================
> 
> There are two possible paths to take on mobile:
> 
> 1. Design FHR so it functions like a responsive Sandstone-style page. SUMO
> must follow this convention, at least for the FHR article page. How do we do
> this?
> 
> 2. Design FHR so it functions more like a Firefox OS app. SUMO doesn’t need
> to be redesigned, but FHR might not match the style of the rest of the
> browser chrome

I favor option 3: design FHR so that it matches the rest of Fennec. That's Bug 883935. It's only HTML for ease of implementation. The mocks I've seen from Ian (see Bug 883935) use some of the styling cues of Sandstone (e.g., the electric blue links), but it's not quite the same.

I'm not concerned that SUMO appears different: it *is* different. A visual style change reinforces that this is live, webby content from human beings -- a support site -- rather than a local experience that simply happens to invisibly fetch some of its content from a CDN.

If we end up wanting to reconcile these, we can resolve SUMO theming differences at a later date.


> Move or mirror the FHR article page out of SUMO and host it on mozilla.org.
> This way, the page style automatically becomes responsive Sandstone. The
> concern here is article maintenance

This is what I understand the plan to be. We don't want the fundamental "what is FHR, and what is our privacy policy" explanation to change frequently. It should be static HTML on mozilla.org, *exactly like the existing desktop PP*:

https://www.mozilla.org/en-US/legal/privacy/firefox.html#health-report


> WHAT WILL HAPPEN TO THE PRIVACY POLICY PAGE
> ===========================================
> 
> The privacy policy page will need to be redesigned to follow whichever path
> we choose to take. We’ll need to file a bug for this.

This is that bug, no?
(In reply to Richard Newman [:rnewman] from comment #4)

> I favor option 3: design FHR so that it matches the rest of Fennec. That's
> Bug 883935. It's only HTML for ease of implementation. The mocks I've seen
> from Ian (see Bug 883935) use some of the styling cues of Sandstone (e.g.,
> the electric blue links), but it's not quite the same.

Yup, neither desktop nor mobile FHR are meant to reflect the Sandstone web style. They are meant to reflect a more common styling for our Firefox in-content UI. Again, Sandstone is not the look we are after here.
(In reply to Ian Barlow (:ibarlow) from comment #5)
> (In reply to Richard Newman [:rnewman] from comment #4)
> 
> > I favor option 3: design FHR so that it matches the rest of Fennec. That's
> > Bug 883935. It's only HTML for ease of implementation. The mocks I've seen
> > from Ian (see Bug 883935) use some of the styling cues of Sandstone (e.g.,
> > the electric blue links), but it's not quite the same.
> 
> Yup, neither desktop nor mobile FHR are meant to reflect the Sandstone web
> style. They are meant to reflect a more common styling for our Firefox
> in-content UI. Again, Sandstone is not the look we are after here.

Fully agree with Ian on this. It's a native page and not any web page… It should not be confused with our other web properties. 

Some other alternatives:
https://dl.dropboxusercontent.com/u/124776818/misc/fennec-health-report-design-draft%20v1.pdf

We can have the learn more page link to a HOME>>ABOUT page that is built into FHR -- it tells what FHR is and provides links to the privacy policy and the SUMO page

Thoughts?

Also, do all of us agree that the SUMO page and the privacy page should have sandstone style  as shown in the following pages?

SUMO (not responsive yet)
https://support.mozilla.org/en-US/kb/firefox-health-report-understand-your-browser-perf

PRIVACY POLICY (responsive)
http://www.mozilla.org/en-US/privacy/policies/firefox-os/#top
Flags: needinfo?(rnewman)
Flags: needinfo?(ibarlow)
Flags: needinfo?(bram)
(In reply to Arun Balachandran Ganesan [:abc] from comment #6)

> We can have the learn more page link to a HOME>>ABOUT page that is built
> into FHR -- it tells what FHR is and provides links to the privacy policy
> and the SUMO page
> 
> Thoughts?

We don't want to ship localized content with the browser. I'm not overly concerned whether we host the descriptive content as part of the FHR app or elsewhere on m.o.


> Also, do all of us agree that the SUMO page and the privacy page should have
> sandstone style  as shown in the following pages?

Yes to the privacy page, no opinion on SUMO.
Flags: needinfo?(rnewman)
(In reply to Richard Newman [:rnewman] from comment #7)
> (In reply to Arun Balachandran Ganesan [:abc] from comment #6)
> 
> > We can have the learn more page link to a HOME>>ABOUT page that is built
> > into FHR -- it tells what FHR is and provides links to the privacy policy
> > and the SUMO page
> > 
> > Thoughts?
> 
> We don't want to ship localized content with the browser. I'm not overly
> concerned whether we host the descriptive content as part of the FHR app or
> elsewhere on m.o.

Thanks, Richard. 

For others: I just spoke with Richard and we agree that we could have the same page to be a webpage that is hosted somewhere instead of being local. Nothing about how it looks or behaves changes except that it's not local. How does that sound to everyone else?

> > Also, do all of us agree that the SUMO page and the privacy page should have
> > sandstone style  as shown in the following pages?
> 
> Yes to the privacy page, no opinion on SUMO.

Cool. As per my conversation with Bram, we agreed to 'sandstone' the privacy page'. The SUMO page design will not be modified now – we will wait on that one.
I will continue to think of ways to better integrate SUMO’s mobile visual style — at least for the FHR help portion of it — with Sandstone. At the moment, however, it’s not a critical concern.
Flags: needinfo?(bram)
(In reply to Bram Pitoyo [:bram] from comment #9)
> I will continue to think of ways to better integrate SUMO’s mobile visual
> style — at least for the FHR help portion of it — with Sandstone. At the
> moment, however, it’s not a critical concern.

Agree. Thanks, Bram!
Depends on: 885385
For reference, the privacy policy page that we are looking to make responsive is located here:
http://www.mozilla.org/en-US/legal/privacy/firefox.html

Due to time limitation, it might be best to just adopt an existing responsive design already used on the Persona Terms of Service page:
http://www.mozilla.org/en-US/persona/privacy-policy/
Thanks, Bram. We are currently using the privacy policy you have listed first to be consistent with what we have on desktop. We will hopefully come back to it later and have someone change the design for the mobile and desktop pages together.
Flags: needinfo?(ibarlow)
Priority: -- → P5
Whiteboard: [measurement:client]
lets be sure we are using the correct url here
See https://bugzilla.mozilla.org/show_bug.cgi?id=1497137; component deprecated.
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → INCOMPLETE
Product: Firefox Health Report → Firefox Health Report Graveyard
You need to log in before you can comment on or make changes to this bug.