pulley vs scroll: Accidental selection of pulley menu items while scrolling
asked 2013-12-28 10:26:00 +0300
Many a times while scrolling to view the contents in apps, on reaching the page ends, pulley menu is pulled out. And to make the things worse, this also selects some option in the menu including critical ones like 'delete'. If many are experiencing this, kindly consider a gui improvement to differentiate the in-app scroll from pulley menu drawing. Thanks.
Original Post:. I've been thinking about a way to work around the limitations of the pulley UI approach, and I have come across the following potential solution: firm versus gentle swipe.
I came across this idea when I noticed that in the browser I could not scroll by swiping around the thumb if I was pressing it firmly against the glass, while a gentler touch made it possible.
Of course, the ideal approach would be with hardware capable of detecting the actual pressure (which the current hardware does not), but if the areas is able to detect the size of the touch area (which I think the current hardware does), it should be possible (in fact, it _is_, considering what I see with the browser).
The only underside I see to this approach is that the touch 'width' might need some tuning to be calibrated for the specifc user (we don't all have equal fingers), although some form of automatic 'training' would be possible.
This sounds kind of difficult
AL13N ( 2013-12-28 10:32:07 +0300 )editwhy difficult? in fact, to me it would appear more natural: normal swiping gives you interaction with the app 'front', while a firm press (and swipe) goes ‘beyond’ the front, as if you were shifting the topmost sheet in a pile to see what's behind.
bilog ( 2013-12-28 10:35:12 +0300 )editCould be natural for somebody, unintuitive for others. I think this kind of differentiation must be introduced carefully, it can do much more damage than good
Titanium ( 2013-12-28 13:02:06 +0300 )editRemember the N800 that could differentiate between stylus and finger use (it was a resistive touchscreen) and offer different UI for each? It never really worked reliably well.
pycage ( 2013-12-28 15:05:24 +0300 )editThe stylus vs finger thing is IMO a different source of problems.
Maybe instead of firm vs gentle swipe we can consider swipe vs press and swipe, sort of like we have tap (click/select) vs long tap/hold (right click/show context menu).
bilog ( 2013-12-28 15:30:58 +0300 )edit