Closed Bug 1244701 Opened 4 years ago Closed 4 years ago

Message EOL plan to gingerbread users

Categories

(Firefox for Android :: General, defect)

defect
Not set

Tracking

()

RESOLVED FIXED
Firefox 47
Tracking Status
firefox47 --- verified
relnote-firefox --- 47+
fennec 47+ ---

People

(Reporter: Margaret, Assigned: liuche)

References

Details

Attachments

(2 files, 2 obsolete files)

We should do something similar to what we did in bug 1220720, but we'll need a new string, since the one for that bug explicitly mentions Android 3.

Maybe we can come up with a more generic string that we could use for all future EOL message?

Right now we have:
"Firefox no longer supports Android 3"

How about something like:
"Firefox no longer supports the Android version running on your device"

With a link to a SUMO article explaining what we actually support. I don't know how much users even really know they're running Android "3" vs. another version.
Flags: needinfo?(bbermes)
Good idea +1

Will add this to the Aha card.
Flags: needinfo?(bbermes)
Matej, would you mind helping us with the copy.

We need to make sure that we stay generic with the message but actually letting users know that the upcoming version of Firefox (not their current one they just updated) won't support their OS anymore.

"The next version after your current Firefox version will no longer support the Android version running on your device" or something like this.
Flags: needinfo?(matej)
Below are a few options. Let me know if any of these works.


The next Firefox update will no longer support this version of Android.

The next Firefox update will no longer support your current version of Android.

Future Firefox updates will no longer support this version of Android.

Firefox will no longer support your current version of Android after this update.

This is the last Firefox update that supports your current version of Android.
Flags: needinfo?(matej)
Thanks so much.

I like: "Firefox will no longer support your current version of Android after this update."

Any issue with char count, Margaret/Anthony.
Flags: needinfo?(margaret.leibovic)
Flags: needinfo?(alam)
"Firefox will no longer support your current version of Android after this update." is my pick too! but when I compare it to our current, it feels a tad long:

"Firefox no longer supports Android 3"

Matej do you have thoughts on this? might not be too much shorter but I think every bit helps, just in case!"

"Firefox will no longer support your Android version after this update."
Flags: needinfo?(alam) → needinfo?(matej)
(In reply to Anthony Lam (:antlam) from comment #5)
> "Firefox will no longer support your current version of Android after this
> update." is my pick too! but when I compare it to our current, it feels a
> tad long:
> 
> "Firefox no longer supports Android 3"
> 
> Matej do you have thoughts on this? might not be too much shorter but I
> think every bit helps, just in case!"
> 
> "Firefox will no longer support your Android version after this update."

I think that works fine, but is it clear that we're talking about an update of Firefox rather than an update of Android? I think the word "current" helped clarify, but maybe we should look at one of the other options instead.
Flags: needinfo?(matej)
Thanks for the quick reply!

Hm, maybe we don't need to mention "after this update"? If it shows up in a similar context as we did for bug 1220720...

we do also have a "Tap to learn more" underneath..

> > +----------------------------------------------------------------+
> > |                                                                |
> > |  +-+  Firefox no longer supports your current Android version  |
> > |  +-+  Tap to learn more                                        |
> > |                                                                |
> > +----------------------------------------------------------------+

This might still be too long ^ any ideas for how we can shorten slightly? My hope is that even if there is cutoff, it happens somewhere between "current" and "Android". That way the user can probably guess the rest. 

My worry with "Firefox will no longer support your current version of Android after this
update." is that the cut off might somewhere between "current" and "version", but that leaves "after this update" behind which I think is more important.
Flags: needinfo?(matej)
What I don't like about 'Firefox no longer supports your current Android version' is that it's ambiguous, given they just updated to a new version of Firefox. 

In my mind's eye, I think the message is closer to 'Firefox will no longer support your current Android version' / Tap to learn more'
I think Karen makes a good point. The copy in comment 7 sounds like it won't work now, rather than in the future.

How about the last option I offered in comment 3?

"This is the last Firefox update that supports your current version of Android."
Flags: needinfo?(matej)
(In reply to Matej Novak [:matej] from comment #9)
> I think Karen makes a good point. The copy in comment 7 sounds like it won't
> work now, rather than in the future.
> 
> How about the last option I offered in comment 3?
> 
> "This is the last Firefox update that supports your current version of
> Android."

I like this one! but I have concerns about character length. Could we shorten somehow and align with the guidelines for notifications a bit more [1]? 

How do you feel about these Matej?

> > +---------------------------------------------------------------------+
> > |                                                                     |
> > |  +-+  Your Android version will no longer be supported by Firefox   |
> > |  +-+  Tap to learn more                                             |
> > |                                                                     |
> > +---------------------------------------------------------------------+

> > +---------------------------------------------------------------------+
> > |                                                                     |
> > |  +-+  Update your Android version to get future Firefox updates   |
> > |  +-+  Tap to learn more                                             |
> > |                                                                     |
> > +---------------------------------------------------------------------+

> > +---------------------------------------------------------------------+
> > |                                                                     |
> > |  +-+  To continue getting Firefox updates, please update your Android version   |
> > |  +-+  Tap to learn more                                             |
> > |                                                                     |
> > +---------------------------------------------------------------------+

as always, appreciate the feedback

[1] https://www.google.com/design/spec/style/writing.html
Flags: needinfo?(matej)
(In reply to Anthony Lam (:antlam) from comment #10)
> (In reply to Matej Novak [:matej] from comment #9)
> > I think Karen makes a good point. The copy in comment 7 sounds like it won't
> > work now, rather than in the future.
> > 
> > How about the last option I offered in comment 3?
> > 
> > "This is the last Firefox update that supports your current version of
> > Android."
> 
> I like this one! but I have concerns about character length. Could we
> shorten somehow and align with the guidelines for notifications a bit more
> [1]? 
> 
> How do you feel about these Matej?
> 
> > > +---------------------------------------------------------------------+
> > > |                                                                     |
> > > |  +-+  Your Android version will no longer be supported by Firefox   |
> > > |  +-+  Tap to learn more                                             |
> > > |                                                                     |
> > > +---------------------------------------------------------------------+

This could still be interpreted as something happening now, rather than in the future.

> > > +---------------------------------------------------------------------+
> > > |                                                                     |
> > > |  +-+  Update your Android version to get future Firefox updates   |
> > > |  +-+  Tap to learn more                                             |
> > > |                                                                     |
> > > +---------------------------------------------------------------------+
> 
> > > +---------------------------------------------------------------------+
> > > |                                                                     |
> > > |  +-+  To continue getting Firefox updates, please update your Android version   |
> > > |  +-+  Tap to learn more                                             |
> > > |                                                                     |
> > > +---------------------------------------------------------------------+

Do we prompt users to upgrade their OS in other instances? Could there be a case where upgrading is impossible, in which we're just making this frustrating for them?

I would prefer to focus on Firefox and what we're doing.

Maybe we just have to live with a longer string here?
Flags: needinfo?(matej)
Almost all (guessing less than <1%) these users have no user serviceable upgrade. If they have an upgrade then they have been ignoring it for years.
Let's just go with this then, it aligns better with the platform.

 > +---------------------------------------------------------------------+
 > |                                                                     |
 > |  +-+  Firefox will no longer support your current version of Android after this update.   |
 > |  +-+  Tap to learn more                                             |
 > |                                                                     |
 > +---------------------------------------------------------------------+
tracking-fennec: ? → 47+
Works for me.
Assignee: nobody → liuche
Flags: needinfo?(margaret.leibovic)
I see the link in the AHA card, but it points to a gingerbread-specific link, but I don't think this is quite right - I agree with comment #1 that we should just have everything point to a single link that lists the versions that are supported/no longer supported.

We should maybe keep the Honeycomb link up to provide info to people who already have our Honeycomb EOL messaging but haven't opened Firefox to see it (?) but we shouldn't support a specific SUMO page for every version we EOL.
Flags: needinfo?(jsavage)
Flags: needinfo?(bbermes)
Attached image Screenshot: Notification string too long (obsolete) —
Upon testing this, the notification string is much too long. Gingerbread doesn't support expanded notifications, so there is no way to display the whole title the way we can on Honeycomb+.
Flags: needinfo?(alam)
The other string proposed is also a bit too long.
(In reply to Chenxia Liu [:liuche] from comment #17)
> Created attachment 8719040 [details]
> Screenshot: Notification string too long
> 
> Upon testing this, the notification string is much too long. Gingerbread
> doesn't support expanded notifications, so there is no way to display the
> whole title the way we can on Honeycomb+.

I was afraid of this... thanks for testing them out!
Flags: needinfo?(alam) → needinfo?(matej)
^oops, hit the enter key by accident.

Matej, how do you feel about something shorter that front loads the message?

"Update your Android version to get future Firefox updates" would be the suggestion I can think of. 

To :kbrosnan 's point, it might not always be an option. But I think that's our best option. A "Your Android version is no longer supported" seems not so helpful.. Open to other ideas you have though!
I would disagree that we should suggest updating the Android version - it's definitely not actionable, and basically requires the user to buy a new phone. Ideally we could come up with a string that is not too long - we *know* the string will get cut off in pretty much every Gingerbread device that displays this message.

What about "This version of Android is too old" and "Tap to learn more"?

If we did that we'd want to use this string just for Gingerbread. (We'd use a longer, more descriptive string for any subsequent EOLs, though I don't think we're going to EOL anything else soon.) Another thing to note for Gingerbread is that you can't swipe to dismiss notifications the way you can on newer versions of Android, so if the user interacts with this notification, they *will* be taken to the SUMO page - maybe that affects how much information we feel we need to cram into this message. On the flip side, if the user closes/updates Firefox without tapping the notification, we don't show it again.
Unfortunately I think we're going to have to live with something that isn't ideal and that may even sound curt and incomplete (and hope that the user clicks to learn more). Here's what I'm thinking:

Firefox will no longer update

OR

This is your last Firefox update

I know those sound scary, even misleading, but I'm struggling to think of something that will fit the space. Do we know what the exact character count that we're working with is?
Flags: needinfo?(matej)
(In reply to Matej Novak [:matej] from comment #22)
> Firefox will no longer update

All things considered, I think this one is our best option.
Flags: needinfo?(bbermes)
Barbara, needinfo-ing you because I think the AHA card isn't right, because we wanted a single EOL SUMO page. Can you update the AHA card with the correct link if that's the case?

> I see the link in the AHA card, but it points to a gingerbread-specific
> link, but I don't think this is quite right - I agree with comment #1 that
> we should just have everything point to a single link that lists the
> versions that are supported/no longer supported.
> 
> We should maybe keep the Honeycomb link up to provide info to people who
> already have our Honeycomb EOL messaging but haven't opened Firefox to see
> it (?) but we shouldn't support a specific SUMO page for every version we
> EOL.
Flags: needinfo?(bbermes)
Comment on attachment 8718958 [details]
MozReview Request: Bug 1244701 - Message EOL plan to gingerbread users. r=margaret

Review request updated; see interdiff: https://reviewboard.mozilla.org/r/34813/diff/1-2/
Attachment #8718958 - Attachment description: MozReview Request: Bug 1244701 - Message EOL plan to gingerbread users. → MozReview Request: Bug 1244701 - Message EOL plan to gingerbread users. r=margaret
Attachment #8718958 - Flags: review?(margaret.leibovic)
Attachment #8718958 - Flags: review?(margaret.leibovic)
Comment on attachment 8718958 [details]
MozReview Request: Bug 1244701 - Message EOL plan to gingerbread users. r=margaret

https://reviewboard.mozilla.org/r/34813/#review31965

::: mobile/android/base/java/org/mozilla/gecko/BrowserApp.java:805
(Diff revision 2)
> -            if (!prefs.getBoolean(HONEYCOMB_EOL_NOTIFIED, false)) {
> +            if (!prefs.contains(HONEYCOMB_EOL_NOTIFIED) && !prefs.contains(GINGERBREAD_EOL_NOTIFIED)) {

I think we should just use a single pref. No app is ever going to be in a state where it was notified on both honeycomb and gingerbread.

At this point, I don't think it's worth renaming the key itself, but we could rename the variable to just be `EOL_NOTIFIED`.

::: mobile/android/base/locales/en-US/android_strings.dtd:777
(Diff revision 2)
> +<!ENTITY gingerbread_eol_notification_title "&brandShortName; will no longer update">

Instead of putting "gingerbread" in the entity name, I think we should just call this `eol_notification_title`. Then we can use it for all future EOL notifications.
Comment on attachment 8718958 [details]
MozReview Request: Bug 1244701 - Message EOL plan to gingerbread users. r=margaret

Review request updated; see interdiff: https://reviewboard.mozilla.org/r/34813/diff/2-3/
Attachment #8718958 - Flags: review?(margaret.leibovic)
The new string fits fine in the notification bar, and I've stripped out the Honeycomb code as well.

Hm, of note: I was having trouble building this locally with the Gingerbread mozconfig, at https://wiki.mozilla.org/Mobile/Fennec/Android/AdvancedTopics#Building_Gingerbread-only
Attachment #8719040 - Attachment is obsolete: true
Attachment #8719043 - Attachment is obsolete: true
Comment on attachment 8718958 [details]
MozReview Request: Bug 1244701 - Message EOL plan to gingerbread users. r=margaret

https://reviewboard.mozilla.org/r/34813/#review32033
Attachment #8718958 - Flags: review?(margaret.leibovic) → review+
See https://mozilla.aha.io/comments/6251879119976804505.

Will update this bug once I know the URL or Joni can post it here. 

Thanks
Flags: needinfo?(bbermes)
Can we just land this with a generic URL? Or make a best guess? What about:

https://support.mozilla.org/1/mobile/%VERSION%/%OS%/%LOCALE%/eol

Then we can use this for all future EOL notifications without needing to update the URL.

I just don't want this to slip through the cracks before the merge.
Flags: needinfo?(liuche)
We've made the article more generic so it can apply to GB and HC. I've also set it up so that the link in comment #31 will point to this article: https://support.mozilla.org/kb/unsupported-version
Flags: needinfo?(jsavage)
Release Note Request (optional, but appreciated)
[Why is this notable]: Notify Gingerbread Users that Firefox will no longer update after this release
[Suggested wording]: Notify Gingerbread Users that Firefox will no longer update after this release
[Links (documentation, blog post, etc)]: https://support.mozilla.org/en-US/kb/unsupported-version
relnote-b2g: --- → ?
Release Note Request (optional, but appreciated)
[Why is this notable]:
[Suggested wording]:
[Links (documentation, blog post, etc)]:
relnote-firefox: --- → ?
relnote-b2g: ? → ---
Comment on attachment 8718958 [details]
MozReview Request: Bug 1244701 - Message EOL plan to gingerbread users. r=margaret

Review request updated; see interdiff: https://reviewboard.mozilla.org/r/34813/diff/3-4/
Hi Joni, I was waiting for the final say in url before landing this, so I didn't end up using the url suggested in comment #31.

Instead, since it's still good to preserve the locale/os/version components of the url, I'm using https://support.mozilla.org/1/mobile/%VERSION%/%OS%/%LOCALE%/unsupported-version in order to be consistent with the actual SUMO page mentioned in comment #32.

Could you update the redirect for this link instead?

Thanks for the patience and work here, I'm glad we're wrapping this up :)
Flags: needinfo?(liuche)
https://hg.mozilla.org/mozilla-central/rev/f3b3ade07154
Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → FIXED
Target Milestone: --- → Firefox 47
Tested using:
Device: HTC Desire HD (Android 2.3.5)
Build: Firefox for Android 47.0a1 (2015-03-01)
A notification is displayed in the android notification bar: "Nightly will no longer update. Tap to learn more".
Tapping it, a new tab opens, but with the message "Page Not Found".
Here is the link: https://support.mozilla.org/1/mobile/47.0a1/Android/en-SG/unsupported-version
Whoops, I forgot to actually flag Joni in comment #37 so the url is probably not live. Joni, could you add a redirect for the other url that I ended up using? Thanks.
Flags: needinfo?(jsavage)
Sure thing. I've set up the URL from comment #37 so that it redirects to the article.  I tried Teodora's link in comment #39 and it seems to work now.

Let me know if there's anything else!
Flags: needinfo?(jsavage)
Added to Fx47 (Aurora) release notes.
A system notification is displayed in the notification bar informing users that "Aurora will no longer update". Tapping it, a new tab opens with an article saying that Firefox will no longer be supported on Gingerbread. 

Verified as fixed using:
Device: One A2001 (Android 5.1.1) 
Build: Firefox for Android 47.0a2 (2016-03-09)
QA Contact: teodora.vermesan
You need to log in before you can comment on or make changes to this bug.