Revision history [back]

I have seen no user-created application implement its settings by utilizing the Sailfish settings menu. I'm afraid people either aren't really aware of its existence (easy to forget (which ironically is good)) or deem it an unnecessary way of complicating things.

I reckon the very essence of the ideas behind Sailfish is that most frequently used applications and features are presented as simply and with as few obstacles as possible. One of the ways to implement and make use of this idea is to separate the (less frequently needed) configuration features from those that make the application into what it is. This keeps the pulley menus tidier etc. and when configuration is needed, the user will know where to look since it's all in the same place for every application.

It's a new approach as is dropping the buttons and thus needs some getting used to, but both are necessary for the simple usage of the OS.

So what I'm hoping is that the design guidelines for Sailfish applications would disclose the preferred approach to implementing application settings since it's a fairly fundamental feature of the platform. Perhaps it would help to emphasize this idea while the whole ecosystem is still new and developing fast.

Or do people generally find separated app settings an undesired feature? Discuss.

I have seen no user-created application implement its settings by utilizing the Sailfish settings menu. I'm afraid people either aren't really aware of its existence (easy to forget (which ironically is good)) or deem it an unnecessary way of complicating things.

I reckon the very essence of the ideas behind Sailfish is that most frequently used applications and features are presented as simply and with as few obstacles as possible. One of the ways to implement and make use of this idea is to separate the (less frequently needed) configuration features from those that make the application into what it is. This keeps the pulley menus tidier etc. and when configuration is needed, the user will know where to look since it's all in the same place for every application.

It's a new approach as is dropping the buttons and thus needs some getting used to, but both are necessary for the simple usage of the OS.

So what I'm hoping is that the design guidelines for Sailfish applications would disclose the preferred approach to implementing application settings since it's a fairly fundamental feature of the platform. Perhaps it would help to emphasize this idea while the whole ecosystem is still new and developing fast.

Or do people generally find separated app settings an undesired feature? Discuss.

I have seen no user-created application implement its settings by utilizing the Sailfish settings menu. I'm afraid people either aren't really aware of its existence (easy to forget (which ironically is good)) or deem it an unnecessary way of complicating things.

I reckon the very essence of the ideas behind Sailfish is that most frequently used applications and features are presented as simply and with as few obstacles as possible. One of the ways to implement and make use of this idea is to separate the (less frequently needed) configuration features from those that make the application into what it is. This keeps the pulley menus tidier etc. and when configuration is needed, the user will know where to look since it's all in the same place for every application.

It's a new approach as is dropping the buttons and thus needs some getting used to, but both are necessary for the simple usage of the OS.

So what I'm hoping is that the design guidelines for Sailfish applications would disclose the preferred approach to implementing application settings since it's a fairly fundamental feature of the platform. Perhaps it would help to emphasize this idea while the whole ecosystem is still new and developing fast.

Or do people generally find separated app settings an undesired feature? Discuss.

I have seen no user-created application implement its settings by utilizing the Sailfish settings menu. I'm afraid people either aren't really aware of its existence (easy to forget (which ironically is good)) or deem it an unnecessary way of complicating things.

I reckon the very essence of the ideas behind Sailfish is that most frequently used applications and features are presented as simply and with as few obstacles as possible. One of the ways to implement and make use of this idea is to separate the (less frequently needed) configuration features from those that make the application into what it is. This keeps the pulley menus tidier etc. and when configuration is needed, the user will know where to look since it's all in the same place for every application.

It's a new approach as is dropping the buttons and thus needs some getting used to, but both are necessary for the simple usage of the OS.

So what I'm hoping is that the design guidelines for Sailfish applications would disclose the preferred approach to implementing application settings since it's a fairly fundamental feature of the platform. Perhaps it would help to emphasize this idea while the whole ecosystem is still new and developing fast.

Or do people generally find separated app settings an undesired feature? Discuss.

I have seen no user-created application implement its settings by utilizing the Sailfish settings menu. I'm afraid people either aren't really aware of its existence (easy to forget (which ironically is good)) or deem it an unnecessary way of complicating things.

I reckon the very essence of the ideas behind Sailfish is that most frequently used applications and features are presented as simply and with as few obstacles as possible. One of the ways to implement and make use of this idea is to separate the (less frequently needed) configuration features from those that make the application into what it is. This keeps the pulley menus tidier etc. and when configuration is needed, the user will know where to look since it's all in the same place for every application.

It's a new approach as is dropping the buttons and thus needs some getting used to, but both are necessary for the simple usage of the OS.

So what I'm hoping is that the design guidelines for Sailfish applications would disclose the preferred approach to implementing application settings since it's a fairly fundamental feature of the platform. Perhaps it would help to emphasize this idea while the whole ecosystem is still new and developing fast.

Or do people generally find separated app settings an undesired feature? Discuss.