1846081 - Create user experience heartbeat prompt for Nightly

Status: NEW

(Firefox for Android :: General, enhancement, P3)

Description

[Joe M [:jmahon]]

Recently, we've had some incidents and stability issues that we would have benefit from noticing earlier in our release trains. While a portion of what we should monitor is in the form of automated information (e.g. crash reports or play store ratings), we could also stand to benefit from enabling our users to give us some direct feedback from a non-disruptive prompt within the app.

So, we want to try out a simple tactic to allow us to get qualitative feedback from Nightly users on a regular-enough basis to inform us if an issue seems to start emerging.

The nature of this feature hasn't been decided, but we're pretty flexible in what it winds up appearing like. The conditions we want to meet are:

• Extremely simple to implement (under 1 week to design & implement)
• Extremely non-disruptive (for instance: showing up as an easily-dismissable snackbar or a widget on the homepage would be plenty)
• Easy to opt out
• Nightly only (we want to encourage Nightly users to be "pack leaders" who are more willing to give feedback, rather than just people who want, for instance, more add-ons. If they don't want to deal with this kind of prompt, they may be better suited to be on Beta instead)
• It should be simple and self-explanatory. The end goal would be a super-passive, thoughtless "👍" every time they see it, until such a time that they have an actual issue.
• Might be worth nudging people towards Bugzilla (for reporting issues) or Mozilla Connect (for requesting features), e.g. through an information ([ i ]) prompt. However, if we want to do this, we'd need a decision brief about it, because it could lead to increased traffic in our already-overburdened Bugzilla backlog, or an increase in traffic to our SUMO-moderated Connect page.
• Should show up with appropriately non-annoying frequency (e.g. maybe monthly) but often enough, across all the user population, for us to get decent enough volume of responses to provide a useful continuous baseline.

Once deployed, we would get a baseline satisfaction score, and then monitor that score to see if it ever dips below whatever threshold we agree on.

Some additional context from the thread that inspired this meta: https://mozilla.slack.com/archives/C05F3DJDGBB/p1690391324305809

Comment 1

[BugBot [:suhaib / :marco/ :calixte]]

The meta keyword is there, the bug doesn't depend on other bugs and there is no activity for 12 months.
:rsainani, maybe it's time to close this bug?