Perceived responsiveness of the UI

Design
#14

Thanks. Since this is doable by a patch it means that is something it can be changed easily.

The current settings is something that makes SFOS feel slow. Jolla can tweak this.

1 Like
#15

I’ve used it before, and it was great. Unfortunately, it doesn’t work on SFOS 3.4. Somebody has to fix it or repack it for 3.4

#16

I updated the patch to work on 3.4.
https://coderus.openrepos.net/pm2/project/patch-animation-settings-iii

3 Likes
#17

Thank you so much. I hope it will also work on SFOS 4.0.1.48, because I am running that version at the moment.

#18

Thank you so much! The difference is huge, at least in my opinion. The feeling is for a completely different phone :grinning:
In my opinion, this should be part of the factory settings. Thanks again!

1 Like
#19

I updated the patch to work on 4.0.1.48.

3 Likes
#20

Amazing! Thank you very much.

#21

Thanks a lot for the patch !
Is there a way to custom the swipe to event view speed animation please ?

#22

To me it feels like SF has a delay in reacting to a scroll. Indeed it even flashes an item in a list as if it was selected, before the scroll starts. This leads to a constant sense of the UI being sluggish.

#23

Yes the somehow sluggish scroll is there. The flash however is a reaction to touch. And is unrelated to the scroll. The nintendo switch interface does it also.
Android -at least the device i test- “hides” it by delaying the item selection. I have no idea how iOS handles that.

#24

I think Sailfish is using very simplistic algorithms(?) for transitions in ui. It doesn’t react to different accelerations applied when swiping, ie physics of swipes seems unnatural when compared to for example Nokia N9 or very natural feel of Miui from Xiaomi. And transitions are slow too, or linear and thats why seemingly slower? I’m no programmer myself, just trying to put to words the perceived differences compared to my other phones.

2 Likes
#25

It may or may not be unrelated, but it is disturbing as it hints at an interaction happening with that particular element, even though you are scrolling a whole list and not concerned about an individual item… On other platforms there is a flash too, but only if you actually clearly press on the item to open it or select it. I would venture that it would feel more tactile to delay the flash ever so slightly, so it doesn’t appear when scrolling.

Obviously the scrolling also should not be delayed, as that makes it feel sluggish.

1 Like
#26

I’d also like to see it go. I am not defending it.

2 Likes
#27

I also want to add:

  • Keyboard appearing when taping a text field.
  • Browser bar appearing when scrolling.

In general every transition of the os is waaaaayyyy tooo slow.

1 Like
#28

One more thing is how long it takes before an alarm you dismissed or snoozed finally stops occupying the screen. The sound and vibrations are muted as soon as you dismiss, but the reminder stays on screen for what feels like an eternity and prevents you from doing anything else unless you wait for it to go away or swipe from the left/right side. It should disappear as soon as you select ‘Dismiss’, without any delay.

1 Like
#29

Just coming back to this because i got to play with an ios device. iOS uses the same solution as android. From the time you touch there is a delay in the flash. If you touch and scroll immediately the “flash”/reaction to touch doesn’t happen.

SFOS can solve it the same way (introduce a delay) i believe.

#30

I definitely believe some simple tweaks on that could give the appearance of more fluidity. The delay seems very short, but perhaps that is all that is needed, and a little bit of fuzziness about how much finger movement is considered enough for the flash to be cancelled and for scrolling to start.

#31

The topic -general feel of the OS- was disused in a community meeting a few weeks back and joona was made aware of this topic. There is not ETA though since some areas require a newer Qt.

#32

I’d like to add to the already mentioned points:

  • screen wake up animation is too slow
  • with the finger already on the fingerprint sensor, it won’t unlock the device right away, instead, you have to lift the finger and tap again

This, in addition to the general inaccuracy of the fingerprint sensor results in multiple trial&error attempts rather than quick and straight unlocking.
I have so say though that compared to the XA2 the 10ii sensor is worse, but positioned better. The XA2 sensor was more precise, however being on the backside, it was always like tapping a few times to hit it.

Also:

  • swiping from left screen inside to show the homescreen often doesnt work. I have to carefully position the finger to make it work. often I need several attempts
  • same for the swipe-down to close
  • it would be nice to light up the display by tapping it, or have the accelerometer enable it

When compared to gestures on e.g. the iPhone (the one with FaceID / no home button), I am always stunned by just how precise it is and well it works.

Those are small things, and surely non-critical. However its those small things that turn a mediocre/good user experience into a great user experience.
Or the other way round: Not done right it introduces annoyances which accompany the user all the time and might lead to frustration sooner or later.

1 Like
#33

I’ve found this to be a problem mostly on the Xperia 10 II. I’ve had some wrong edge swipes on the Jolla 1, Tablet, C and Xperia X, but it’s very noticeable on the Xperia 10 II.