Closed Bug 1306045 Opened 8 years ago Closed 5 years ago

Improve the default browser prompt experience

Categories

(Firefox :: Shell Integration, defect)

defect
Not set
normal

Tracking

()

RESOLVED FIXED
Tracking Status
firefox52 --- wontfix

People

(Reporter: canuckistani, Unassigned)

References

Details

We should test not prompting users to become the default browser on first run:

* we had a patch that did a notificationbox instead, we should tesst that out as oppoosed to the current modal dialog
* we should consider doing it on second run or something

On desktop systems the workflow of users running some software and clicking a link in that software to open in a default browser is much less common than it used to be, largely due to the widespread adoption of web-based email. We've had some people propose that integrating into the quicklaunch toolbar or Win10 desktop tiles is far more valuable for visibility than being default on Windows.

Note: one recent trend that works against this is the widespread use of electron-based web app wrappers, for example slack. If a user is using slack, they are much more likely to care what browser is the default.
We did this test but I don't seem to be able to find the bug. We also tested how often Firefox is opened from another app - Bug 1276027 - Jared knows more about this.

The UX thinking on this currently is that we shouldn't prompt on first run but pinning to your taskbar and making it your default browser should be one of the onboarding experiences that we present to users (we have various ideas of where and when this would be). The modal is prompt on startup is still good for when Firefox has had it's default status switched away.
Flags: needinfo?(jaws)
(In reply to Verdi [:verdi] from comment #1)
> We did this test but I don't seem to be able to find the bug. We also tested
> how often Firefox is opened from another app - Bug 1276027 - Jared knows
> more about this.

I happened to talk to cmore about the at lunch - he related to me that the modal default browser prompt had no impact on retention.

> The UX thinking on this currently is that we shouldn't prompt on first run
> but pinning to your taskbar and making it your default browser should be one
> of the onboarding experiences that we present to users (we have various
> ideas of where and when this would be). 

Agreed. I think we can do something minimal here ( eg the previously proposed notificationbox solution that was in dev edition for a while )

> The modal is prompt on startup is
> still good for when Firefox has had it's default status switched away.

In this particular case we should do something but I don't think a modal prompt is necessarily the right answer either. We should test this.

cc'ing cmore.
Component: General → Shell Integration
Flags: needinfo?(jaws)
Mass wontfix for bugs affecting firefox 52.

We actually did this. We no longer ask on firstrun.

cmore, can you confirm?

Flags: needinfo?(chrismore.bugzilla)

I believe yes, but my brain is foggy about that specific detail. Let's ask Jim Thomas if he can confirm.

Flags: needinfo?(chrismore.bugzilla) → needinfo?(jimthomas)

We don't ask on firstrun, although there are some followup prompts on restart.

Flags: needinfo?(jimthomas)

I'm going to mark this fixed then.

Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.