We have moved to a new Sailfish OS Forum. Please start new discussions there.
1 | initial version | posted 2015-09-05 18:43:49 +0200 |
Cover actions were one of the best and most used (at least for me) features of Sailfish 1.0. The change that came in the new UI converted the gestures to buttons (and limiting them to one for official apps, but that's another story).
While I understand the need for rethinking horizontal swipes as triggers for the cover actions (it would interfere with the carousel navigation), I think that the chosen solution is worse than removing the cover actions altogether (which I'd hate to see).
I have never accidentally triggered a cover action in Sailfish 1.0, but I am constantly triggering them in 2.0.
It is a big problem, so I am proposing either rethinking the trigger to something more useful and intuitive, or removing cover actions altogether. I for one will be removing cover actions from my apps, if this doesn't change before the final version of Sailfish 2.0 UI.
PS: I admit I am writing this a bit angry - I was trying to make a calendar event and needed to check an e-mail to find the details. When coming back from an e-mail, I accidentally hit the '+' action of the Calendar app and everything was lost.
It might also seem that this is a duplicate of a previous post about cover actions, but this is purely a post based on the user experience with Sailfish 2.0, therefore the first of its kind.
2 | No.2 Revision |
Cover actions were one of the best and most used (at least for me) features of Sailfish 1.0. The change that came in the new UI converted the gestures to buttons (and limiting them to one for official apps, but that's another story).
While I understand the need for rethinking horizontal swipes as triggers for the cover actions (it would interfere with the carousel navigation), I think that the chosen solution is worse than removing the cover actions altogether (which I'd hate to see).
I have never accidentally triggered a cover action in Sailfish 1.0, but I am constantly triggering them in 2.0.
It is a big problem, so I am proposing either rethinking the trigger to something more useful and intuitive, or removing cover actions altogether. I for one will be removing cover actions from my apps, if this doesn't change before the final version of Sailfish 2.0 UI.
A call for other users - please provide possible solutions as comments to this post.
PS: I admit I am writing this a bit angry - I was trying to make a calendar event and needed to check an e-mail to find the details. When coming back from an e-mail, I accidentally hit the '+' action of the Calendar app and everything was lost.
It might also seem that this is a duplicate of a previous post about cover actions, but this is purely a post based on the user experience with Sailfish 2.0, therefore the first of its kind.
3 | retagged |
Cover actions were one of the best and most used (at least for me) features of Sailfish 1.0. The change that came in the new UI converted the gestures to buttons (and limiting them to one for official apps, but that's another story).
While I understand the need for rethinking horizontal swipes as triggers for the cover actions (it would interfere with the carousel navigation), I think that the chosen solution is worse than removing the cover actions altogether (which I'd hate to see).
I have never accidentally triggered a cover action in Sailfish 1.0, but I am constantly triggering them in 2.0.
It is a big problem, so I am proposing either rethinking the trigger to something more useful and intuitive, or removing cover actions altogether. I for one will be removing cover actions from my apps, if this doesn't change before the final version of Sailfish 2.0 UI.
A call for other users - please provide possible solutions as comments to this post.
PS: I admit I am writing this a bit angry - I was trying to make a calendar event and needed to check an e-mail to find the details. When coming back from an e-mail, I accidentally hit the '+' action of the Calendar app and everything was lost.
It might also seem that this is a duplicate of a previous post about cover actions, but this is purely a post based on the user experience with Sailfish 2.0, therefore the first of its kind.
4 | No.4 Revision |
Cover actions were one of the best and most used (at least for me) features of Sailfish 1.0. The change that came in the new UI converted the gestures to buttons (and limiting them to one for official apps, but that's another story).
While I understand the need for rethinking horizontal swipes as triggers for the cover actions (it would interfere with the carousel navigation), I think that the chosen solution is worse than removing the cover actions altogether (which I'd hate to see).
I have never accidentally triggered a cover action in Sailfish 1.0, but I am constantly triggering them in 2.0.
It is a big problem, so I am proposing either rethinking the trigger to something more useful and intuitive, or removing cover actions altogether. I for one will be removing cover actions from my apps, if this doesn't change before the final version of Sailfish 2.0 UI.
A call for other users - please provide possible solutions as comments to this post.
PS: I admit I am writing this a bit angry - I was trying to make a calendar event and needed to check an e-mail to find the details. When coming back from an e-mail, I accidentally hit the '+' action of the Calendar app and everything was lost.
It might also seem that this is a duplicate of a previous post about cover actions, but this is purely a post based on the user experience with Sailfish 2.0, therefore the first of its kind.
5 | retagged |
Cover actions were one of the best and most used (at least for me) features of Sailfish 1.0. The change that came in the new UI converted the gestures to buttons (and limiting them to one for official apps, but that's another story).
While I understand the need for rethinking horizontal swipes as triggers for the cover actions (it would interfere with the carousel navigation), I think that the chosen solution is worse than removing the cover actions altogether (which I'd hate to see).
I have never accidentally triggered a cover action in Sailfish 1.0, but I am constantly triggering them in 2.0.
It is a big problem, so I am proposing either rethinking the trigger to something more useful and intuitive, or removing cover actions altogether. I for one will be removing cover actions from my apps, if this doesn't change before the final version of Sailfish 2.0 UI.
A call for other users - please provide possible solutions as comments to this post.
PS: I admit I am writing this a bit angry - I was trying to make a calendar event and needed to check an e-mail to find the details. When coming back from an e-mail, I accidentally hit the '+' action of the Calendar app and everything was lost.
It might also seem that this is a duplicate of a previous post about cover actions, but this is purely a post based on the user experience with Sailfish 2.0, therefore the first of its kind.
6 | No.6 Revision |
Cover actions were one of the best and most used (at least for me) features of Sailfish 1.0. The change that came in the new UI converted the gestures to buttons (and limiting them to one for official apps, but that's another story).
While I understand the need for rethinking horizontal swipes as triggers for the cover actions (it would interfere with the carousel navigation), I think that the chosen solution is worse than removing the cover actions altogether (which I'd hate to see).
I have never accidentally triggered a cover action in Sailfish 1.0, but I am constantly triggering them in 2.0.
It is a big problem, so I am proposing either rethinking the trigger to something more useful and intuitive, or removing cover actions altogether. I for one will be removing cover actions from my apps, if this doesn't change before the final version of Sailfish 2.0 UI.
A call for other users - please provide possible solutions as comments to this post.
PS: I admit I am writing this a bit angry - I was trying to make a calendar event and needed to check an e-mail to find the details. When coming back from an e-mail, I accidentally hit the '+' action of the Calendar app and everything was lost.
It might also seem that this is a duplicate of a previous post about cover actions, but this is purely a post based on the user experience with Sailfish 2.0, therefore the first of its kind.
7 | retagged |
Cover actions were one of the best and most used (at least for me) features of Sailfish 1.0. The change that came in the new UI converted the gestures to buttons (and limiting them to one for official apps, but that's another story).
While I understand the need for rethinking horizontal swipes as triggers for the cover actions (it would interfere with the carousel navigation), I think that the chosen solution is worse than removing the cover actions altogether (which I'd hate to see).
I have never accidentally triggered a cover action in Sailfish 1.0, but I am constantly triggering them in 2.0.
It is a big problem, so I am proposing either rethinking the trigger to something more useful and intuitive, or removing cover actions altogether. I for one will be removing cover actions from my apps, if this doesn't change before the final version of Sailfish 2.0 UI.
A call for other users - please provide possible solutions as comments to this post.
PS: I admit I am writing this a bit angry - I was trying to make a calendar event and needed to check an e-mail to find the details. When coming back from an e-mail, I accidentally hit the '+' action of the Calendar app and everything was lost.
It might also seem that this is a duplicate of a previous post about cover actions, but this is purely a post based on the user experience with Sailfish 2.0, therefore the first of its kind.
8 | No.8 Revision |
Cover actions were one of the best and most used (at least for me) features of Sailfish 1.0. The change that came in the new UI converted the gestures to buttons (and limiting them to one for official apps, but that's another story).
While I understand the need for rethinking horizontal swipes as triggers for the cover actions (it would interfere with the carousel navigation), I think that the chosen solution is worse than removing the cover actions altogether (which I'd hate to see).
I have never accidentally triggered a cover action in Sailfish 1.0, but I am constantly triggering them in 2.0.
It is a big problem, so I am proposing either rethinking the trigger to something more useful and intuitive, or removing cover actions altogether. I for one will be removing cover actions from my apps, if this doesn't change before the final version of Sailfish 2.0 UI.
A call for other users - please provide possible solutions as comments to this post.
PS: I admit I am writing this a bit angry - I was trying to make a calendar event and needed to check an e-mail to find the details. When coming back from an e-mail, I accidentally hit the '+' action of the Calendar app and everything was lost.
It might also seem that this is a duplicate of a previous post about cover actions, but this is purely a post based on the user experience with Sailfish 2.0, therefore the first of its kind.