New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 619566 link

Starred by 2 users

Issue metadata

Status: Duplicate
Merged: issue 632893
Owner:
Closed: Jul 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: All
Pri: 3
Type: Bug



Sign in to add a comment

DevTools: Device Mode UX difficult to find options

Project Member Reported by jonathan.garbee@chromium.org, Jun 13 2016

Issue description

The current flow to enable a non-touch emulation is:

1. Know DM overflow menu exists and click on it
2. Toggle "Add device type" setting
3. Go back to main UX and find the new dropdown
4. Open and toggle to a "(no touch)" option.

This means that developers *must*:

1. Know the overflow menu is what it is
2. Know what "Device Type" contains
3. Know that "Add" options reveal a new setting in the main UX.

The new UX is extremely simple, however it comes at an increasing cost of developers not understanding what everything does. Most at least know the overflow menu exists, but few know what "Device Type" does. It isn't clear and we shouldn't expect developers to experiment so much to try and figure things out.

In this instance, wouldn't it be clearer when in "Responsive" mode to have a "touch" toggle checkbox. Having I'm not sure what exactly changes with Mobile/Desktop toggles other than automatically changing the emulated size which isn't necessary either. A checkbox to handle the emulation type when in this mode would be much clearer. Then devices have it predefined so we just hide the toggle when emulating a device directly. This would remove one of the overflow menu items and make the UX far clearer to our users.
 
We decided to hide most options to encourage the default mobile+touch+hidpi setup. In theory, most users should not need anything else. Paul?
Mergedinto: 632893
Status: Duplicate (was: Untriaged)

Sign in to add a comment