Submenus for Pulley? [not relevant]

asked 2014-06-16 14:29:23 +0300

veeall gravatar image

updated 2014-07-12 17:04:17 +0300

simo gravatar image

I've been thinking about Sailfish ui and find that when apps grow more sophisticated, there would arise a need to have more commands on menus, thus sooner or later you have to introduce submenus to pulley items and also to the context menus of a longpressed items. And i personally can imagine such menu system, and it imo really fits into pulley paradigm, though navigating only by thumb could prove harder, possibly.

So i make this my feature suggestion - first level pully menu could slide aside when a menu item with submenu is selected, swype on a secondary level menu item would navigate back into parent menu - just get visual clues and animations right and it should work.

I edited my original suggestion above, this following opinion is now deprecated (:

Also, i think bottom pulley menu should be deprecated, to me they look like messy workaround for not being able to place more items to top pulley menu.

My other concern as Jolla 1 phone user is, that if features accumulate, the OS wouldn't become a resource hog and obsolete my jolla too early due to low specs it has. I'd like to being able to use my phone 2-4 years.

edit retag flag offensive reopen delete

The question has been closed for the following reason "question is not relevant or outdated" by veeall
close date 2014-07-12 14:17:31.412113



I think bottom pulley menu should be deprecated.

Why exactly? Actually, I like the idea of having two levels of menus available - however, I think that there should be some sort of implementation guide, providing recommendations for developers on how they should use them, e.g. PullDownMenu for context-related and/or often-accessed functionality like "Bookmark this" or "View details about this" as opposed to PushUpMenu for global and/or fewer accessed stuff like "Settings" or "About".

tokaru ( 2014-06-16 14:45:56 +0300 )edit

Bottom menu too often jumps up when scrolling through lists, i find it really annoying. Also ui would look cleaner if there is no pulley visual indicator at bottom, be it only on top, imho.

veeall ( 2014-06-16 14:52:46 +0300 )edit

Thanks for clarification, I understand what you mean... but IMHO this is mainly an issue with the user experience not being consistent across applications because of missing implementation guidelines

tokaru ( 2014-06-16 15:06:59 +0300 )edit

I like PushUpMenus, but agree that having two glowing indicators on the same page doesn't look very clean. What's worse, some developers (yes, Communi, MeeCast, Sailimgur, I'm looking at you) implement some type of 'side pulley menu' which isn't selectable by pulling/pushing at all, but then having 3-4 visual indicators on one page is really ugly and unintuitive.

I think there should be clear guidelines, otherwise we just have to contact developers one by one and ask them to act sanely :)

nodevel ( 2014-06-16 15:52:28 +0300 )edit

I don't think the bottom pulley menu is bad, rather the way developers implement both top and bottom pulley menus which is frustrating and shouldn't be done - like in Mitäkuuluu where all options in the top menu of a conversation could be put somewhere else without losing functionality, don't hate me coderus.

And, as nodevel mentioned, the side pulley menus are a bit weird and don't seem to fit with the general Sailfish UI paradigm.

nthn ( 2014-06-16 16:25:23 +0300 )edit