965374 - [android] Consider a mechanism for proactively surfacing notices based on Health Report data

Status: RESOLVED INCOMPLETE

(Firefox Health Report Graveyard :: Client: Android, defect)

Description

[Richard Newman [:rnewman]]

In particular: ABP right now is causing problems. FHR knows that you have it installed, and it knows if your startup time is bad. Why can't we help you?

Comment 1

[Robert Kaiser]

Dave Zeber and the metrics team have been working on getting something like this for desktop, I guess you have Android in mind here?

That said, we might be able to leverage similar process on the backend for this.

Comment 2

[Richard Newman [:rnewman]]

(In reply to Robert Kaiser (:[e-mail]) from comment #1)
> Dave Zeber and the metrics team have been working on getting something like
> this for desktop, I guess you have Android in mind here?

Yeah, see bug component and platform :P


> That said, we might be able to leverage similar process on the backend for
> this.

Got a link to any docs or bugs? (Dave?)

Comment 3

[Dave Zeber [:dzeber]]

We've been working on detecting common browser problems using FHR data, which would trigger a "user tip" to show and inform the user. So far we've been looking at common problems surfacing in SUMO and figuring out how to determine that they are happening from the FHR data. A writeup of what we have so far is in this Gdoc: https://docs.google.com/a/mozilla.com/document/d/1EWuPjxZxWE8oT2VgFjyZjLxVuMHpdkrkYavhkZLVtrQ/edit?usp=sharing. 

The tricky thing is to be confident enough that the slowdown is caused by ABP (in your case) and not anything else going on with your profile, as there is a certain cost associated with showing the user unreliable alerts.

I'm sure the backend implementation of this type of feature on Android would be similar.

Comment 4

[Firefox Bug Husbandry Bot]

Per https://bugzilla.mozilla.org/show_bug.cgi?id=1497137, this component is deprecated. Resolving this bug as incomplete, per :sdaswani.