Move to Front/Back Order is Backwards on iPad

[Bryan Rieger]

Every time I have to move something forward or backward on the iPad I'm always caught up that 'Move to Back' is at the top, while 'Move to Front' is at the bottom - the same order as the desktop apps. This order might work on desktop, but it's counterintuitive on the iPad.

Please consider reversing the order with 'Move to Front' at the top of the list and 'Move to Back' at the bottom, ie:

• Move to Front
• Move Forward One
• Move Back One
• Move to Back

Also, is the '…One' really necessary? Can it be set to Two or Three? If not, it doesn't really communicate anything useful.

[fde101]

Considering that when you look at the layers panel objects which are on top are listed toward the top of the panel, I tend to agree it makes more sense to reverse these, probably on the desktop apps also.

[carl123]

7 hours ago, Bryan Rieger said:

I'm always caught up that 'Move to Back' is at the top, while 'Move to Front' is at the bottom - the same order as the desktop apps.

On Windows this is the order...

• Move to Front
• Move Forward One
• Move Back One
• Move to Back

[Meliora spero]

In UX practice, the order of these commands is based on frequency of use and intuitiveness. "Move to Front" is typically prioritized, as it is the most used for bringing objects to the top. "Move Forward One" follows, being commonly used for minor adjustments. "Move Back One" comes next, as it is less frequent but still intuitive. Finally, "Move to Back" is last, as it is rarely needed to send objects all the way to the back.

[fde101]

I move to front or back much more often than I move by one in either direction.  How often they are used will vary enough between users and workflows that I don't think it is reasonable to assume that rationale in determining their order.