| Thread Previous • Date Previous • Date Next • Thread Next |
I think the true solution is to show the toolbar by default on the deep page stack pages. I read a quote somewhere that when developing Ubuntu Phone apps, they need to be Ubuntu in character meaning configurable but usable by our grand parents (simple but powerful?). I think the toolbar is the only way to achieve this. My preferred solution is the Evernote route:
I wonder if the toolbar should be visible by default on 'page stack' pages. I think that the page context requires it. I can only envision 2 types of scenario where page stack is used:(1) Navigation to a destination (drilling down through lists).(2) Destination (information of some kind that requires an action, whether adding, editing or navigating away via the 'Back' button).If this is actually the case and I'm not blind to other scenarios, I see that enforcing a chrome-less, full screen view without a toolbar would be detrimental to the experience. I feel that if the toolbar was visible on page stack sub pages, it would still be in-line with the spirit of using full screen to enable the best possible user experience (where appropriate).Taking it one step further, the toolbar could be shown by default on page stack sub pages, but hidden when the use begins scrolling, this idea comes from Evernote on iPhone when editing a note.However, I must concede that a visible toolbar wouldn't be anywhere near as attractive and clean as the current hidden-by-default toolbar!
I think we must consider the loss of the home button on the device and how disorientating it can be to rely on gestures alone (I remember my first use of a windows 8 tablet).
Novelty and 'flabby' ideas has crept into my thinking re gestures on this and it may have spread to others too! ;)
Simplicity is king. Lou On 12/06/13 12:54, Josh Leverette wrote:
Simon, This would introduce design complexity by the way that the user may accidentally activate this gesture or fail to activate this gesture and have negative consequences. It needs to be something that does not interact with the current gestures, unless we're willing to drop an existing gesture function to be replaced with this one. The beauty of Pin to Exit is that it requires a short tap, then a tap which is held, then moving the finger in a given direction. It would interfere with nothing existing, and probably nothing in the future either, and it would allow for an aesthetically pleasing removal of the top layer as the finger moves, gripping it. This is as opposed to acting after the gesture is complete, in an irreversible method.Sincerely, JoshOn Jun 12, 2013 6:51 AM, "Petar Koretic'" <petar.koretic@xxxxxxxxx <mailto:petar.koretic@xxxxxxxxx>> wrote:"Last one for a while I promise. What about a pinch from both the left and right sides - together, like I'm closing up this page 'cause I'm done with it" If I may this is more of "close this app gesture", however I'm not sure when somebody really needs a back button since swiping from right gives last app and swiping from left will get you to home screen? "nice tight little "<" like symbol in the top left title bar to navigate back. It's small but visually clean, consistent and works." On the other hand this sounds great (some kind of back button i titlebar) and it can be seen in other OSes. using more than on hand to do it really doesn't seem practical, -- Mailing list: https://launchpad.net/~ubuntu-phone <https://launchpad.net/%7Eubuntu-phone> Post to : ubuntu-phone@xxxxxxxxxxxxxxxxxxx <mailto:ubuntu-phone@xxxxxxxxxxxxxxxxxxx> Unsubscribe : https://launchpad.net/~ubuntu-phone <https://launchpad.net/%7Eubuntu-phone> More help : https://help.launchpad.net/ListHelp
| Thread Previous • Date Previous • Date Next • Thread Next |
