Ask / Submit

Combine app close and pulley menu

asked 2013-12-25 16:29:49 +0300

TuukkaH gravatar image

updated 2015-10-08 01:20:55 +0300

simo gravatar image

This way, there wouldn't be two very similar gestures, and it would always be possible to open the pulley menu via swipe-from-top even where it's not possible in the current design. In this new design, every app would have a pulley menu at least for closing the app. Currently, it's a problem that the pulley can't be accessed all the time in apps such as Maps (fullscreen map), Browser (fullscreen web content), and with apps that have fullscreen vertical lists (can't access pulley without scrolling all the way up first).

Closing the app could be one of the pulley menu entries, or it could be activated by pulling/swiping all the way down past all the normal entries.

Edit: Lifting this old question up, as it's topical after, and would IMO improve the new UI. This question was voted down (322 views, -1) when it was introduced for earlier UI

Edit2: Only 7 votes after lift up, should this be closed as outdated? (original above is from Dec 2013)

edit retag flag offensive close delete


This would seem impractical in a lot of scenarios, e.g. to be able to use a pulley menu in the browser you'd have to scroll all the way back to the top of the page first.

Elleo ( 2013-12-25 18:09:03 +0300 )edit

Once you get used to the paradigm there's a fairly clear division between in-app gestures (pulley menu, changing pages, accept dialogs, etc.) and system wide gestures (closing apps, peaking at home screen/minimising apps, displaying events feed).

Elleo ( 2013-12-25 18:11:04 +0300 )edit

@Elleo, Perhaps I explained it badly, but the impracticality that you explain is actually with the current situation, and my proposal would fix it: in my proposal, the pulley would always be accessible via the swipe-from-top gesture regardless of the app state.

TuukkaH ( 2013-12-25 18:57:33 +0300 )edit

@Elleo, Regarding the logic of in-app vs. system-wide gestures, I think opening the pulley could be seen as a system-wide action (comparable to the top-of-the-screen menu bar in Ubuntu and Macs).

TuukkaH ( 2013-12-25 19:00:16 +0300 )edit

Ah, sorry, I hadn't realised that you intended for pulley menus to be accessed via the swipe gesture.

Elleo ( 2013-12-25 19:07:52 +0300 )edit

@Elleo, thanks for the feedback, reworded the idea trying to clarify the problem and the solution.

TuukkaH ( 2013-12-25 19:21:05 +0300 )edit

So do you suggest that pulley menu would include closing the app and would only be accessible by swiping down, or that it would be accessible both pull and swipe down?

parasemic ( 2013-12-25 19:23:35 +0300 )edit

2 Answers

Sort by » oldest newest most voted

answered 2013-12-26 17:19:19 +0300

jsiren gravatar image

Since the device has a multitouch screen, the pulley could always open with a two-finger pull.

edit flag offensive delete publish link more

answered 2013-12-25 20:10:31 +0300

miqu gravatar image

I have to disagree also. Swipe from top to close app is fine. There are different ways that they used to get pulley menu available for instance in the gallery you can tap to get the menu visible.

For the problem of long lists I might suggest a maemoish way to solve it. Three quick scroll swipes and it scrolls really fast to the end. Or maybe double touch for pulley...

edit flag offensive delete publish link more



The current way of closing apps isn't the problem, accessing the pulley menu is. Like you mention, access to menu currently varies from app to app adding unnecessary complexity. For example, to perform a search in the Maps app, you have to select (any) unrelated location on the map first - insane!

TuukkaH ( 2013-12-25 21:07:39 +0300 )edit
Login/Signup to Answer

Question tools

1 follower


Asked: 2013-12-25 16:29:49 +0300

Seen: 518 times

Last updated: Oct 08 '15