Silica: Add small delay before pulley menus appear [not relevant]
Silica (the sailfish UI) has some annoying behave that I think can be killed "very easy":
This may seem like a small issue but I am sure many users see below issue as an annoying behave. So please vote this if you agree. Because stuff like this scares away non geeks/possible new users who had used Iphone, Symbian, Android before and want to test something fresh :)
In this case I talk about Pulley menus.
When for example reach "end of page" the pulley menu appears to fast and you may accidently select a menu item. This could be easy fixed:
Add a small delay around lets say 1 second? before the pulley menu goes visble.
Same goes for "start of page" when scolling backward.
Ofcourse this can be done "per app" but it seems like a hack if every app have to add delays to pulley menus and I think this should be done in lower UI layers...
while this might make sense in some specific app, I don't think this should be implemented system wide. IMHO the Pulley menue should be accessed latency-free. Even a short 1-sec-delay is probably annoying after some time. I think new users get pretty fast used to the current behavior of Pulley menu.
blubdibub ( 2014-01-05 18:01:30 +0200 )editSince pulley menu activates vibration, there is an immediate indication that something "unusual" has happened. The other way round: A delay of 1 or even 0.5 second would result in many people not finding out about pulley menu. (And I would be very annoyed having to wait each time I want to access the pulley menu for an artificial time-out.)
jgr ( 2014-01-05 21:27:48 +0200 )editThere are a few places where the pulley menu appearing may be unintentional and the OS could prevent its display.
Eg. scrolling through a long list of tweets you might be rapidly flicking the screen to get to the top. The pulley menu should not be shown if your finger has left the screen.
aegis ( 2014-01-06 02:02:59 +0200 )editto make it more clear I mean when you scroll fast to end of page. The delay dont have to be one second maybe 100 msec is enought...
mike7b4 ( 2014-01-07 02:19:46 +0200 )editI think the real issue is that you have to flick so many times to reach the top or bottom. If there was a quicker way (tapping on the top, like iPhone, or something else), then the pulley wouldn't be activated by mistake so easily. I mean it doesn't come down with a normal scroll, you have to flick a 2nd time to open it. Additionally some clear indication you have scrolled to the end (iOS bounce is genius).
Setok ( 2014-03-05 22:21:10 +0200 )edit