undefined

points

[-]

Have done small to medium institutional rollouts of Firefox in different orgs, some of which were on top of a Linux base and others a Windows base. Windows deployments include Firefox in the base image and configuration is managed with AD and Ansible. Linux deployments manage configuration with Ansible. The preinstalled browsers were removed or disabled.

All users received an orientation and were informed that Firefox is the only approved browser.

Firefox was pinned to the desktop and taskbar, usually with the name "INTERNET" as the web browser is commonly known here.

The number of support tickets was very small. Usually if a user reported a problem with the web browser, it was a page that was also broken in Chrome or some other network issue.

Users reacted positively when they saw that there are no ads in Firefox. uBlock Origin was preinstalled.

Without ads and tracking scripts the web browser is massively faster, which also was perceived by users.

If there is any initial resistance to Firefox, it usually melts quickly.

The only bother has been the frequent UI updates to Firefox, which occasionally cause frustration until we apply a new configuration to revert whatever fresh horrors Firefox designers have birthed. With ESR, these problems are less frequent.

I hope this Firefox Enterprise freezes the UI to the classic "tabs look like tabs" aesthetic, maintaining the option of vertical tabs.

by j454 hours ago|

parent|

[-]

I briefly read institutional as 'intentional', with both in mind, the standardization of experience is something that's really wroth thinking about.

One feeling I am starting to get is server side web apps might make more of a re-emergence, because putting so much application and business logic in the front end serves as a bigger footprint for possible security issues.

With respect to resistance to browsers (or preference for something else), I agree that users seek familiarity and those who got to start with Firefox do still remember it.

Mozilla is just one org, but it's relative independence will hopefully provide other perspectives to using a web browser as a universal interface, not just for humans, but our new sentence-dna containing friends.

by dkenyser7 hours ago|

prev|

[-]

I wish this was true. At my org we had to add Chrome to the base image because otherwise we get so many tickets/calls about it even though we provide it via an internal software distribution service that any user has access to. People like what they like and are very resistant to change.

by j454 hours ago|

parent|

[-]

I wish that was true too.

I remember one place simply changed the icon and watched the issues drop.

People really can be creatures of habit.

Some enterprises i've seen put in their own icon for a web browser (imagine starting with an intranet) and that helps separate it a bit more.

This might not be for everyone, nor ideal in all cases but people seemed to be OK with the idea of having a dashboard to launch their work from.