Having remorses for your remorse timer redesign?
asked 2019-12-17 00:26:20 +0300
@jovirkku please pass this on to Martin or whomever is the responsible dev right now
The new design for remorse items is a disimprovement!
Before 3.2.1:
swipe away to finish action, tap to abort. easy, mnemonic gesture favoring the safe abort action via a quick tap anywhere on the remorse timer
Now:
Left 3 quarters of remorse item: confirm action, right quarter button like area to abort.
That means: no swipe gesture & minimal accessibility for canceling a remorse action
I'm always rooting for you guys and am trying to be objective.
But honestly have you lost any sense of good UX design?
I mean even the changelog shows that someone wasn't particularly enthusiastic about this change:
[sailfishsilica] Adapt remorse to yet another design.
Habits are hard to change. Before 3.2.0 and 3.2.1, I had no idea that swipe was to finish action. On 3.2.0, the X button was misleading. The current design in 3.2.1 seems more intuitive than both older designs, but there is still room for improvement. The cancel area needs to be more clearly visible and distinct, maybe a different color or a separating line.
Whatever the design, it needs to be added to the tutorial. That's a SFOS distinct design element, new users need to know about it and how to use it.
orangecat ( 2019-12-17 00:34:15 +0300 )editReally? I have sometimes jumped the gun too early with some of the changes made, but this one... It looks like something from a five minute mock-up and it's as little intuitive as they get. I was baffled when I saw it first, and I'm still not sure what to do, so I just end up waiting for the count-down to end. Sorry Sailors, but that's a do-over.
Tanghus ( 2019-12-17 02:35:12 +0300 )editI just tried it and feel confused. It has four segments now and only if I tap “undo” the action is cancelled. Every other segment acts as “accept”. How would one know that? I suspect many accidental actions. Especially when it’s so easy to make a mistake - a tap in the wrong place and there’s no return, while a swipe was a very conscious action. One mistap has a dire consequence now.
@orangecat: that swipe was “accept” (and that you actually could ignore the countdown and leave the view as an implicit accept) should be in the tutorial (if it wasn’t already). Redesign is the wrong way to go imo.
Mohjive ( 2019-12-17 02:53:53 +0300 )editI agree that it should be more apparent what are does which action.
But actualy, to this day (and I have been using SFOS since launch) I have not been aware that you can actually confirm remorse timers instead of waiting for them to finish counting down. And you do have to wait for them as most apps simply ignore staged remorse timers if you exit a view or close the app.
So definitely still room for improvement & I'm still not convinced enough about remorse timer being actually useful to use them in my apps. ;-)
MartinK ( 2019-12-17 04:47:27 +0300 )edit@MartinK Jolla only added the swipe-to-commit somewhere during SFOS 2 releases. To me, it was the best UX design feature they have added to date (Waiting for the timer to run out everytime was torturous). Why change the design...? If you accidently choose to delete something, a kind of panic sets in and you immediately want to tap the timer to cancel. Doing that now might have the opposite effect - fail! Swiping the timer away was a very conscious and deliberate action (As @Mohjive said). Rather add the usage to the tutorial to educate the users, than redisgning something that was never broken.
Nova ( 2019-12-17 07:29:46 +0300 )editI implore (BEG!) Jolla to re-consider this decision. I see this as a regression.