1821475 - [1.0] Dispatch and show fullscreen message

Status: VERIFIED FIXED

(Fenix :: General, enhancement)

Description

[Roger Yang [:royang]]

Add observer to look for the next full screen message and to display it.
This will need to

1. Decide when to check for new messages.
2. If a full screen message should be shown if already shown before.
3. Deferred showing it. (how long in between full screen messages)

Since these messages are disruptive by design, we'll have to be sure that this doesn't happen to the user too often.

Comment 1

[Roger Yang [:royang]]

For the first implementation, we can assume that:
a. There is only one fullscreen message experiment at a time.
b. We will only show fullscreen message at start of the application.
c. There could be cases we disrupt the users' flow.

Comment 2

[Joe M [:jmahon]]

Just to clarify on

c. There could be cases we disrupt the users' flow.

I think this refers to potential edge cases where a user opens the app from an external source (e.g., clicking a link while it's the default browser) and gets hit with a research surface.

Per (b), the research surface should not appear in the middle of a Firefox session

Comment 3

[Roger Yang [:royang]]

Updated requirement: Don't show full screen message until onboarding is done.

Comment 4

[Roger Yang [:royang]]

Updated requirement: The research surface will slide in from the bottom.

Comment 5

[BMO Github Automation]

Attachment: [mozilla-mobile/firefox-android] Bug 1821475 - Show research surface when survey message is available (#1566)

Comment 6

[BMO Github Automation]

Authored by https://github.com/rocketsroger
https://github.com/mozilla-mobile/firefox-android/commit/7156394fa4e3fc773700418e89f3abe386b52786
[main] Bug 1821475 - Show research surface when survey message is available

Comment 7

[miralobontiu]

Hello,
On a stage experiment and a local stage build from 4/11: selecting to display any message like a fullscreen card does NOT work - nothing is displayed.

I'll remove the qe-verify+ flag.
Roger, could you please add the qe-verify+ when this is actionable?
Thank you!

Comment 8

[Roger Yang [:royang]]

Hi Mira, I'm happy to help on how we can test this experiment. This is the experiment to test with https://experimenter.services.mozilla.com/nimbus/android-research-surface-validation/summary. Let's talk on zoom to discuss what you're seeing and why you don't see the card. Thanks

Comment 9

[Roger Yang [:royang]]

To try to unblock your testing, here's what I did to test:

1. Copy JSON from https://experimenter.services.mozilla.com/nimbus/android-research-surface-validation/summary and paste it in initial_experiment.json.
2. Add a bucket config like so to the json above.
   "bucketConfig": {
   "randomizationUnit": "nimbus_id",
   "namespace": "test-1",
   "start": 0,
   "count": 10000,
   "total": 10000
   },
3. Setup a local release build with personal keystore.
4. Start Fenix and use secret menu to confirm that you're on the control/treatment branch (depends on which test case you're on).
5. Close Fenix, move clock forward 1-2 days, cold start Fenix.

Comment 10

[miralobontiu]

Attachment: 1821475.png

Verified as fixed on a local Release build.
Tested on Oppo Find X3 Lite (Android 11).