We have moved to a new Sailfish OS Forum. Please start new discussions there.

Pulley-Menu vs Context-Menu

asked 2013-12-27 10:48:52 +0300

wout.martens gravatar image

updated 2014-02-07 02:46:17 +0300

chemist gravatar image

Currently the action UI is made in 2 parts - Pully Menu and Long press item Menu. To me this is akward as the pully menu sometimes gives more / less options compared to long press item (specific actions)

In order to have a more consistent approach the long press menu should invoke the pully menu rather than showing a dropdown menu on the item.

In this pully menu the user should be able to select item specific actions as well as actions linked to the app the user is in. e.g. Mail app; Item specific action, reply - mark as read - etc. App specific action, update - select multiple emails - etc

It's just strange to scroll to the top in order to get to the menu. The menu should always come from the thumb (invoke menu on the screen no matter where you are)

edit retag flag offensive close delete


Agreed that it's unintuitive and cumbersome to scroll all the way up in a list to access the application menu. There's a suggestion on alternative ways to activate pulley menus. Add a suggestion there or just vote on your favorite.

Mohjive ( 2014-02-25 12:54:45 +0300 )edit

2 Answers

Sort by » oldest newest most voted

answered 2013-12-28 18:36:49 +0300

Mariusmssj gravatar image

But I think that's the points, a long press works on an single element while pulley menu works on the page. That seems to be consistent throughout the OS

edit flag offensive delete publish link more


Yes could be but it's not logic to go up to the top just to find some actions which are not visible when long pressing an item. My request is a way to find an 'easy' way to invoke pully menu.

wout.martens ( 2013-12-30 10:25:38 +0300 )edit

The context-menu is inconsistent as it is different on different places and there is info hidden beneath your finger you cannot see and there is no haptic feedback! Try to think out of the box please. Closing with an X in the top right corner is consistent over a whole era of computers...

chemist ( 2014-02-07 02:44:17 +0300 )edit

@eric ^^ answer -> comment

chemist ( 2014-02-19 21:28:18 +0300 )edit

@chemist: thanks, done.

eric ( 2014-02-25 11:38:50 +0300 )edit

answered 2014-02-07 02:40:03 +0300

chemist gravatar image

Context-menus should behave like pulley-menus and give away their secrets without moving too much.

What we love about the pulley is that you activate an item without tapping while being able to read it.

That does not work that well with context-menus!

How about having the long-tap activate a pulley-menu with the context and not a menu under your finger you cannot read without moving your finger below it and back up to release at the actual item? There could be a Settings item to configure it to pop down from the top with a vibration locking in the first item in the very second the long-tap is being recognized.

I just showed the device to a friend and that was an inconsistency he recognized within 30seconds (tech-savvy guy).

edit flag offensive delete publish link more


The spatial seperation of a pulley-context-menu might be confusing though.

mlatu ( 2015-10-27 07:52:59 +0300 )edit

Did you read the last words? A user out of another mobile world found it odd to not have the context-menu be a pulley as he'd expect it there instead of under his thumb.

chemist ( 2015-10-27 12:13:13 +0300 )edit

Sure I read them.

Did you read the word "might" in my comment?

To some the spatial seperation might be confusing, to others it might be not at all.

mlatu ( 2015-10-27 13:17:03 +0300 )edit

I can't see the benefit of having context menus as pulleys in the readability sense. You still have to pull it all out to read all available alternatives, which is same as today where you have to move your finger to below the context menu to be able to read them all.

What you gain is consistency, sure. But also here I don't really agree, as pulleys are used for the parent application and context menus are for the individual element and having the pulley handling individual elements is counter-intuitive imo.

Mohjive ( 2015-10-27 13:27:42 +0300 )edit

As I typed that last comment I realized that maybe you meant that the pulley should originate from the top of the element and not the top of the screen, as with application pulleys. Then I actually think you're on to something here and I have to reconsider if it's a bad idea or not.

Mohjive ( 2015-10-27 13:29:06 +0300 )edit
Login/Signup to Answer

Question tools



Asked: 2013-12-27 10:48:52 +0300

Seen: 389 times

Last updated: Feb 07 '14