-
Notifications
You must be signed in to change notification settings - Fork 1.3k
WebExtensions main user interface #6092
Comments
Slightly updated user story, and added design tasks. |
Progress report:
|
in fennec, ublock origin's ui is accessible via the main menu as a normal item. as a user, i think it would be good to have it in fenix as an icon similarly to desktop, but in the menu. this would allow users to have multiple addon icons per line (like the navigation buttons are currently). the ui could come up as a sheet or popup so the experience would be more like desktop than with fennec where tapping the menu item opens the addon ui in a new browser tab. (if this is the wrong place to voice a design opinion, please let me know) |
@brampitoyo, a floating action button that is always visible seems a bit intrusive, if its only function is to list a menu from which extension UIs can be accessed. A sublist in the main menu could list extensions, similar to how the Tools submenu currently functions in Fennec. As @ashkitten said, being able to pin frequently used extensions to a row at the top of the main menu would be very useful, and would cut access times considerably. This would be a dedicated row for extension icons at the top of the main menu that is only visible if at least one extension has been pinned there. The extension icons would function as buttons that open the extension UI. |
@ashkitten wrote:
@dessant wrote:
Thanks for these really useful feedback! ⋮ Main menu balanceOur recent User Research study found that adding more and more menu items into the main menu make features less likely to be used, because what our users love about Fenix seems to be its simplicity and relatively minimal interface. So, I think that we have to finely balance two things:
As @dessant wrote:
Frequently used add-onsI want to emphasise the fact that not all add-ons are used frequently enough to be pinned:
But @dessant’s proposal is worth considering:
Native look and feel for add-on’s main user interfaceI was inspired by @ashkitten’s proposal:
ProposalLet’s combine all of the above together. What do you think about something like this?
Pinning add-ons
The result: It takes 3 taps to access any add-on, and 2 taps if put inside main menu Thoughts? |
it might be good to automatically pin addons, but in my opinion there still should be a way to disable that behavior and manually set what addons are pinned in which position, or hide ones you don't want to see. design-wise, i think one row of icons in the main menu would be good for this. you can probably fit 4 icons neatly in a row there, which gives room for 4 pinned addons or 3 pinned addons and an overflow menu icon if there are more than 4 addons to display if the design of this needs to be implemented in multiple steps, it might make sense to leave a ui for managing order/pinning/hiding addons for later and just implementing it with most recently used order for now |
i also had the idea that it could be possible to put a row of addon icons somewhere in the pull-out sheet, maybe under the normal share and bookmark icons? that would give more screen real estate without cluttering the main menu, and provide a more seamless transition to opening the addon ui inside the already expanded bottom sheet. plus, it might make more sense to put addon buttons alongside other page actions |
While it's a nice idea it's not an option because the Quick Action Bar will be removed, see #4281. |
in terms of the add-on manager, i'd really love it if it were the same as the desktop one |
@brampitoyo, supporting uBlock Origin will enable a bunch of other extensions that use that subset of extension APIs to be installed. I think it would be better to design the UX for pinning now instead of redesigning everything several times, especially because it may also involve user interface changes in other places, such as the extension sheet you mention. Pinning could be configurable from the sheet with the extension list directly, either by touching and holding a list item, or by having a dropdown menu at the right side or the list item, like in about:addons on desktop. One could also just open the details of the extension where a pinning switch is present. It seems that the main menu surface has enough space to allow for 4 pinned extensions in a row, while respecting spacing best-practices for touch interfaces. |
Progress report:
Please do check out the Miro board for the latest progress |
@brampitoyo there is another way we can show add-on nicely through using a separate toolbar for extension on the opposite side of url bar. It would show the extension in front of users while browsing, user don't have to go anywhere else to access it and u could live monitor any add-on changes. If you have a bottom address bar and toolbar can be shown at the top with extensions and vice versa. The both bars can also hide automatically when user scrolls through screen so it will save some space from browser ui while browsing . Some web browsers like samsung browser and opera already have dual toolbar in browser & I don't think it would too much affect the usability by showing two toolbars on both sides and if a user feels like it affects it viewing area or have problems with accessing toolbar it can change to a different approach such as using using main menu for accessing extensions or any other approach for using add-ons. |
@brampitoyo, could you share the Miro board? I haven't been able to find the board you're referring to. |
Terrible. If implemented this should be an optional location for add-on items and not used by default. It takes too much from the already limited space of a smartphone, the proposed UI is really distracting, I doubt that a lot of people will use so many add-ons on the smartphone to make this an useful UI for the big majority of users and, of course, additional toolbars come straight out of hell. (Okay, sorry, the last point wasn't quite serious). |
Closes mozilla-mobile#5630, mozilla-mobile#6069, mozilla-mobile#6092, mozilla-mobile#6091, mozilla-mobile#6124, and mozilla-mobile#6147. Co-authored-by: Simon Chae <chaesmn@gmail.com> Co-authored-by: Arturo Mejia <arturomejiamarmol@gmail.com> Co-authored-by: Christian Sadilek <christian.sadilek@gmail.com> Co-authored-by: Gabriel Luong <gabriel.luong@gmail.com>
Closes mozilla-mobile#5630, mozilla-mobile#6069, mozilla-mobile#6092, mozilla-mobile#6091, mozilla-mobile#6124, and mozilla-mobile#6147. Co-authored-by: Simon Chae <chaesmn@gmail.com> Co-authored-by: Arturo Mejia <arturomejiamarmol@gmail.com> Co-authored-by: Christian Sadilek <christian.sadilek@gmail.com> Co-authored-by: Gabriel Luong <gabriel.luong@gmail.com>
Closes mozilla-mobile#5630, mozilla-mobile#6069, mozilla-mobile#6092, mozilla-mobile#6091, mozilla-mobile#6124, and mozilla-mobile#6147. Co-authored-by: Simon Chae <chaesmn@gmail.com> Co-authored-by: Arturo Mejia <arturomejiamarmol@gmail.com> Co-authored-by: Christian Sadilek <christian.sadilek@gmail.com> Co-authored-by: Gabriel Luong <gabriel.luong@gmail.com>
Closes mozilla-mobile#5630, mozilla-mobile#6069, mozilla-mobile#6092, mozilla-mobile#6091, mozilla-mobile#6124, and mozilla-mobile#6147. Co-authored-by: Simon Chae <chaesmn@gmail.com> Co-authored-by: Arturo Mejia <arturomejiamarmol@gmail.com> Co-authored-by: Christian Sadilek <christian.sadilek@gmail.com> Co-authored-by: Gabriel Luong <gabriel.luong@gmail.com>
Closes mozilla-mobile#5630, mozilla-mobile#6069, mozilla-mobile#6092, mozilla-mobile#6091, mozilla-mobile#6124, and mozilla-mobile#6147. Co-authored-by: Simon Chae <chaesmn@gmail.com> Co-authored-by: Arturo Mejia <arturomejiamarmol@gmail.com> Co-authored-by: Christian Sadilek <christian.sadilek@gmail.com> Co-authored-by: Gabriel Luong <gabriel.luong@gmail.com>
Hi, verified as fixed on the latest ✔️ If the Add-on is installed it will be automatically pinned and listed on the top of the ⋮ Main menu. @brampitoyo - Please review and let me know if any additional testing regarding this matter is needed. |
User Story
As a user, I want to be able to access the main user interface of installed WebExtensions (on desktop, they’re almost always doorhangers) so I can use it.
Dependencies
A-C project board
Acceptance Criteria
Design tasks
┆Issue is synchronized with this Jira Task
The text was updated successfully, but these errors were encountered: