[v2.1] Feature Proposal: USB Storage Toggle in Notifications Tray when USB detected



4 years ago
6 months ago


(Reporter: Synper311, Unassigned)



Firefox Tracking Flags

(Not tracked)



(1 attachment)



4 years ago
I'd like to see the USB Storage toggle more user friendly and quick to access.

webOS accomplished this brilliantly using their Dashboard notifications system, and I think a similar approach in FFXOS would work nearly as well.

Currently, the USB storage option is only accessible to the user from the Settings dialogue. Getting there requires a bit of time, scrolling, and fussing about the UI.

I'd like to see the following:

When FFXOS detects that a USB cable (that has data pins) has been plugged in, it notifies the user that they can enable USB Storage. If they tap the notification, the USB Storage will be enabled (and the USB Storage notification will be pinned to the Notifications tray).

If they miss the notification, or don't tap it, there will be a notification with the toggle in the Notification tray the user can toggle. This notification will NOT clear so long as the phone detects the USB Data cable as plugged in.

In this manner, the user can quickly and easily toggle USB Storage on/off while the connection is maintained, without having to further dive into the System menus to do so.

Comment 1

4 years ago
Created attachment 8467164 [details]
Simple Mock-Up of what this USB Storage Notification could look like using existing resources


4 years ago
Flags: needinfo?(firefoxos-ux-bugzilla)

Comment 2

4 years ago
Bulk editing these for tracking to consider for a release with greater UX changes, and to clear the queue. These are not in scope for 2.2 but are marked for 2.3 planning tracking.
Keywords: ux-userfeedback

Comment 3

4 years ago
Removing ni? flag to clear the queue for 2.2 release issues. Bug is marked for later tracking.
Flags: needinfo?(firefoxos-ux-bugzilla)

Comment 4

6 months ago
Firefox OS is not being worked on
Last Resolved: 6 months ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.