Closed Bug 1324724 Opened 8 years ago Closed 4 years ago

User Press Back key then close the app?

Categories

(Firefox for Android Graveyard :: General, defect, P5)

defect

Tracking

(Not tracked)

RESOLVED INCOMPLETE

People

(Reporter: ryang, Unassigned)

References

Details

Attachments

(1 file)

The symptom happened while a behavior triggered a web-page to next step, if user tried Back key , then the app is closed . (This happened in Sign-in page, Privacy notice/Terms of service page, Manage account page, Forget password….)
Hi Max, Would you please elaborate the symptom a little bit for better understanding its mechanism ?? Thank you very much !!
tracking-fennec: --- → ?
Flags: needinfo?(max)
Summary: Press Back key then close the app? (This happened in Sign-in page, Privacy notice/Terms of service page, Manage account page, Forget password….) → User Press Back key then close the app?
In fennec, we implement some function by webpage as you mentioned. Though we can take some advantage from it(ex. runtime A/B testing; web developer's support), it also breaks user mental stack of Setting/Sign-in function by leaving Setting activity to webpage. We may have to do some research on implementation see if we can create another fragment/activity to preserve the user flow stack. :sebastian What do you think?
Flags: needinfo?(max) → needinfo?(s.kaspari)
tracking-fennec: ? → ---
Priority: -- → P1
Priority: P1 → P2
From my point of view that's the end of the first run tour and both actions end the tour. One of them throws you directly into the browser while the other one opens the sign in page. Is this really a confusing flow? (We have a different bug for having an option to be able to get back to the tour in general). (In reply to Max Liu [:maliu] from comment #2) > We may have to do some research on implementation see if we can create > another fragment/activity to preserve the user flow stack. We could do that. But please remember that this is not just a simple website we display - there's quite some interaction happening so that we end up with an account inside the Android system. The first run tour is also something we want to heavily "play with" next year - running experiments and having custom tours for different countries - this can get complex. Before we invest too much engineering time we should make sure that this moves the needle on any metric we care about and is not actually a distraction.
Flags: needinfo?(s.kaspari)
[triage] Non-critical.
Priority: P2 → P3
Re-triaging per https://bugzilla.mozilla.org/show_bug.cgi?id=1473195 Needinfo :susheel if you think this bug should be re-triaged.
Priority: P3 → P5
We have completed our launch of our new Firefox on Android. The development of the new versions use GitHub for issue tracking. If the bug report still reproduces in a current version of [Firefox on Android nightly](https://play.google.com/store/apps/details?id=org.mozilla.fenix) an issue can be reported at the [Fenix GitHub project](https://github.com/mozilla-mobile/fenix/). If you want to discuss your report please use [Mozilla's chat](https://wiki.mozilla.org/Matrix#Connect_to_Matrix) server https://chat.mozilla.org and join the [#fenix](https://chat.mozilla.org/#/room/#fenix:mozilla.org) channel.
Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → INCOMPLETE
Product: Firefox for Android → Firefox for Android Graveyard
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: