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

Moving touch wrongly interpreted as tap-and-hold in Launcher

asked 2014-03-22 09:54:17 +0300

ssahla gravatar image

updated 2017-05-19 08:14:56 +0300

DarkTuring gravatar image

In the Launcher, sliding your finger in an empty area can be interpreted as a tap-and-hold gesture.

How to reproduce: 1. Have your last app launcher page not full, so there is some empty space on the bottom. 2. Move your finger starting from this empty area either up (so that the icons fade to indicate that there are no more pages) or sideways. 3. The launcher will enter delete/rearrange apps mode.

When sliding your finger on top of app icons, this doesn’t happen – you need to hold your finger still to invoke the delete/rearrange mode. I think this should be the case also in the empty area. (Edit: This can also happen when touching and moving on top of icons, but it's harder to reproduce – I think it depends on where exactly the touch starts: right on top of an icon or in the space between them.)

You can also see this behavior on the Home screen (moving your finger in blank area will activate ”close apps” mode).

There's discussion below on whether this is a bug or not. To me that is not so important; the point is that this behaviour, intended or not, should be changed. Reasons:

  • It creates confusion between gestures: When you're trying to scroll down from the last app screen, you'll enter edit mode instead. That is, you're doing a drag/scroll/swipe gesture, but it is interpreted as a tap and hold. You're trying to do one thing, but something else happens. So, it produces accidental actions. This could be easily avoided if tap-and-hold was activated only when holding your finger still (with some tolerance for accidental movement).
  • I see no practical benefits in the way it works now; no-one needs to use it this way on purpose (activating tap and hold by moving one's finger around). (Ok, that's a guess. I can't be sure what other users do.) Everyone knows that tap and hold is by definition "hold your finger still on the screen". So no harm done by changing it.
edit retag flag offensive close delete



I am also confused by this behavior

Awiecierz ( 2014-03-22 11:21:03 +0300 )edit

Me too, i ve this problem.

Claudio Maradonna ( 2015-01-03 02:03:39 +0300 )edit

Probably not the best possible way to try to give more credit to a personal opinion by stating that "no-one needs to use it like that on purpose" ;) This is a user forum, and there are varying UX conventions and UI designs that some like to use and find them beneficial or non-problematic while others might feel diffrently.

foss4ever ( 2015-01-03 21:31:12 +0300 )edit

@jjaone, like I said, it's my guess; but you're right, such vague claim isn't a strong argument. However, I do believe that this kind of gesture is simply not needed, and removing it would reduce confusion and accidental actions. And yes, that's my opinion, and others might feel differently. :)

No-one knows (sic) each and every user's needs. That's why generalizations must be made if one wants to say anything about ”what users need”. And you can go wrong with generalizations, I admit that.

ssahla ( 2015-01-03 22:25:18 +0300 )edit

@ssahla Guessing is not a very good argument either (atleast UI shouldn't be redesigned based on your guess-work only), and personal opinions should not be made or claimed to be generalized or universal facts ;)

foss4ever ( 2015-01-03 23:18:56 +0300 )edit

4 Answers

Sort by » oldest newest most voted

answered 2016-01-24 14:38:16 +0300

nthn gravatar image

As of Sailfish OS 2.0 this is now half fixed. It no longer happens in the application launcher itself, but it still happens in applications folders.

edit flag offensive delete publish link more

answered 2015-01-03 13:04:29 +0300

thisisme gravatar image

I have had my launcher accidentally entering delete/rearrange mode before, but I cannot reproduce it in the manner described by the OP - in fact I haven't figured out how to reproduce it consistently yet. However if you just tap and hold (not slide) on an empty area in the launcher, it will enter delete mode which in my opinion is consistent and intuitive. I'm on version.

edit flag offensive delete publish link more



I wasn't able to reproduce it either, and holding on an empty area triggered delete, consistently with UI.

magullo ( 2015-01-03 21:18:26 +0300 )edit

You're both right in that it works when holding your finger still, which IMO is the intuitive and ”right” way. But you can enter edit mode also by moving your finger on the screen if you start the gesture from an empty area and move the finger to a direction where there isn't anything to scroll to.

ssahla ( 2015-01-03 22:29:24 +0300 )edit

Yes that's how the UI currently works (and has been working like this ever since the launch). And it is very intuitive and right for edit/delete mode to be triggered in two system.screens consistently regardless of moving the finger slightly on empty space or keeping it still.

foss4ever ( 2015-01-03 23:39:57 +0300 )edit

answered 2015-01-03 20:29:19 +0300

Elias gravatar image

It seems to work as follows:

  1. Tap and hold (Press?) for 1 sec -> enter delete mode
    • only in launcher
    • only when tapping empty part of screen
  2. Tap and move -> Flick in that direction
    • only if there is somewhere to go
  3. So when Flicking into a direction where there is no next screen (Flick into a wall), the screen dims to notify user and after 1 sec the gesture is interpreted as a Tap and hold.

When Flicking into a wall, and gesture originates on top of app icon, the gesture can be continued up. This is similar to behavior in Home screen, where delete mode can't be entered at all.

Seems like a bug, and I suggest to make system recognize Flick into a wall as a Flick, notify by dimming and allow continued movement to other directions.

edit flag offensive delete publish link more


Your description of what happens is incorrect; when finger is placed on some empty space on Launcher or Home screen and kept stationary or moved for abt 1 second the delete/edit mode is triggered in both screens and both cases.Thus the behaviour is fully consistent in two system scrrens and enables the user to enter edit/delete mode regardless of keeping finger still or moving it slightly. Not a bug, but consistent behaviour to enter edit/delete mode -> no need to change the UI.

foss4ever ( 2015-01-03 21:15:00 +0300 )edit

answered 2015-01-02 20:49:03 +0300

this post is marked as community wiki

This post is a wiki. Anyone with karma >75 is welcome to improve it.

updated 2015-01-03 21:24:10 +0300

foss4ever gravatar image

I see no problems in this gesture and behaviour of the device. IMO not a bug, and no need the change the UI because of this.

Edit: what actually happens is that when finger is placed on some empty space on Launcher or Home screen and kept either stationary or moved slightly for about 1+ seconds to any directiion that there is no navigatiion pages, the edit/delete mode is triggered in both screens and regardless of the finger movement. The gesture is thus consistent in two system screens and enables user to enter edit/delete mode even if the finger is moved slightly (in addition to keeping it still). Thus, not a bug, or no need to change or remove this gesture and the action triggered by it.

edit flag offensive delete publish link more



If it's not a bug, why does it only happen when you start swiping on empty space? If the behaviour is intentional, surely it would also work when you start swiping from an icon on the last page?

nthn ( 2015-01-02 22:14:07 +0300 )edit

It is a bug and is still there on Vaarainjärvi. :)

Alex ( 2015-01-02 22:30:45 +0300 )edit

Just another gesture to activate specigic behaviour on Home and Laumch screens, naturally recognized only in empty space cause on the icons it might be confused to Cover action or app activation. Gesture is consistent in two system screens and in both cases the behaviour is as expected, and quite intuitive thus not a bug, but a feature.

foss4ever ( 2015-01-03 00:09:16 +0300 )edit

Ofc anyone here seems to have a right to claim any device behaviour or feature or lack of those as bug, but user declaring a wish or an issue as bug, does not neccesssrily make it such.

foss4ever ( 2015-01-03 00:12:05 +0300 )edit

I don't really care if it's a bug or not. Edited the question to be a bit more agnostic on that & added reasons why I think this behaviour should be changed.

ssahla ( 2015-01-03 09:21:15 +0300 )edit
Login/Signup to Answer

Question tools



Asked: 2014-03-22 09:54:17 +0300

Seen: 569 times

Last updated: May 19 '17