Confirmed users
1,041
edits
Firefox/Features/Installers: Difference between revisions
Jump to navigation
Jump to search
m
Original proposal
(Proofreading) |
m (Original proposal) |
||
| Line 219: | Line 219: | ||
I believe this is conceptually simpler for the end user, easier to work with for us, and solves the testing use cases in a better way than what replacing the binary from under you will accomplish. | I believe this is conceptually simpler for the end user, easier to work with for us, and solves the testing use cases in a better way than what replacing the binary from under you will accomplish. | ||
== Original proposal: Optimize for the majority of users == | |||
(This section is by Robert Strong) | |||
=== Overview === | |||
As I understand the purpose from several discussions starting well over a year ago, we want to increase the number of "regular" users running Aurora and Beta builds where regular is more representative of the majority of Firefox users. If that is the primary goal then we should optimize for that case and the only time we shouldn't optimize for that case is when it prevents power users (developers, web developers, etc.) from being able to use Firefox. | |||
Firefox has never supported side by side installations of release builds without the person performing the installation performing additional steps. For example, on Windows existing shortcuts for a release build will be replaces and on Mac the installation requires installing into a location where there isn't already an installation by dragging the Firefox icon to a location outside of the dmg's user interface. Even with the new proposed naming this will still be the case. | |||
For the web developer case I believe a better solution should be created that doesn't get in the way of us implementing features like channel changing. Sayer brought this up to me recently and we came up with an outline of how this could be accomplished that addresses the naming issue under discussion as well as the pre-existing naming issue when installing multiple releases. | |||
=== Reasons for using the same install name for release, beta, and aurora === | |||
* Channel changing is much simpler. When channel switching there are less options to choose from, less steps to perform, and a single user interface for user user to interact with (About window vs. About window, web page, download manager, and installer) when compared to installing. Simplicity is a key point because of the audience we want to attract. | |||
Windows installation: | |||
# Open the Firefox About window | |||
# Click Link | |||
# Download installer and wait for download to complete | |||
# Launch installer | |||
# Click next | |||
# Click next | |||
# Click install and wait for install to complete. | |||
# Click finish | |||
Channel change: | |||
# Open the Firefox About window | |||
# Click change channel | |||
# Select channel | |||
# Click apply and wait for download to complete. | |||
# Click restart | |||
Note: even if the installer were simplified there is likely no way installing a side by side installation will ever be simpler than changing channels. | |||
* When channel changing the end result is a single installation instead of multiple installations (e.g. Firefox vs. Firefox, Firefox Beta, and Firefox Aurora). For some users I highly suspect they will end up with an unused installation of Firefox just sitting there taking up space. | |||
* When channel changing the end result is a single shortcut in the standard Windows' locations instead of multiple shortcuts in the standard Windows' locations. I highly suspect this will be confusing for some users. | |||
* Metrics has previously tried to find out why there is a drop off between users downloading and the first launch of Firefox and as of today we don't have a good understanding as to why there is this drop off. Channel changing would not be affected by this drop off where as having users download and install almost certainly will be. | |||
==Decisions== | ==Decisions== | ||