Cover actions guidelines

asked 2013-12-29 22:11:30 +0300

strnous gravatar image

updated 2014-02-09 19:06:28 +0300

It would be great if there were guidelines set for cover actions used among the developers of different apps. Same action on any app should use the same direction. I.e. "refresh/update" action should ALWAYS be done by swiping the cover in the same direction. Having two apps which have the same action assigned to the opposite directions is quite confusing.

edit retag flag offensive close delete

Comments

1

Developer guidelines ar appreciated here as long it is should, can and not must ;-)

hardcodes.de ( 2013-12-30 12:21:49 +0300 )edit
2

@hardcodes.de SW-quality control in open-source contexts is usually done with recommendations (like W3C RFC's) but in some cases App-stores can require stricter compliance to some UX or other implementation guidelines. I don't see some 'must' rules to completely out of question, if/when they improve the overall user experience and quality of platform. For example, ”If an app has a refresh-type Cover-action, it SHOULD be the swipe-from-right gesture, and User MUST be provided with a control in the app or system UI to make cover actions consistent in his/her device”

foss4ever ( 2013-12-30 12:41:33 +0300 )edit

As I said, I am fine with that and I totally see the advantage. In the end every developer would benefit, too. If he/she decides not to follow the general style of a platform, the app will get less attractive.

hardcodes.de ( 2013-12-30 13:22:27 +0300 )edit

Similar guidelines should/could be imposed for some common items of the pulley menus (i.e. refresh should be the first position, create new item second)

strnous ( 2013-12-30 22:10:09 +0300 )edit

Guidelines are fine as long as they specify cover actions for common use cases. However special cases must not be limited in store requirements as it could prevent innovative applications from accessing store.

unai_i ( 2014-01-19 23:20:59 +0300 )edit