Revision history [back]

@hansa / @HansA:

Is there a way to be more involved in aspects of device (software) intetaction design, so that when a new device or OS iteration comes out we can know better whether and why we want to buy, and so that we can know if and how our contributions may be improving things?

Wrt the overview info, examples, use cases and interaction-mapping directed graphs made available on this forum would help its users to file questions visually, in a way that would let the interaction design staff and code editing developers zero in more exactly on the issues raised and give better feedback, more clearly and faster.

Moreover, Duplicate mitigation could become part of the Question submission process. The Question's relation to the UI and UE for a specific use case or context and a related chosen step therein will help clarify similar and similarly-positioned issues, and allow Questions likely to be marked Duplicate to instead be automatically linked, and even combine votes for action to amend the common interaction step.

As I perceive it, that would be a better form of online community outreach, better for all related development work flows and better for marketing and sales. It is not just an issue of filing this under forum improvement. There are knock-on effects and all kinds of overworn clichés about virtuous cycles. Maybe this is worth a try. Striving to exceed expectations and demonstrably do so really do circle high above grounded talk of how difficult everything is.

We're here to help! Use what you've got, the work of six experts supported by the people you work for.

Please no-one opine in an answer or comment, seriously or coyly, about how manual forum trawling and belaboured, repetitive, condescending rhetoric is somehow a more real or better dialogue than one supported by automation, visualisation, and distraction reduction.

@hansa / @HansA:

Is there a way to be more involved in aspects of device (software) intetaction design, so that when a new device or OS iteration comes out we can know better whether and why we want to buy, and so that we can know if and how our contributions may be improving things?

Wrt the overview info, examples, use cases and interaction-mapping directed graphs made available on this forum would help its users to file questions visually, in a way that would let the interaction design staff and code editing developers zero in more exactly on the issues raised and give better feedback, more clearly and faster.

Moreover, Duplicate mitigation could become part of the Question submission process. The Question's relation to the UI and UE for a specific use case or context and a related chosen step therein will help clarify similar and similarly-positioned issues, and allow Questions likely to be marked Duplicate to instead be automatically linked, and even combine votes for action to amend the common interaction step.

As I perceive it, that would be a better form of online community outreach, better for all related development work flows and better for marketing and sales. It is not just an issue of filing this under forum improvement. There are knock-on effects and all kinds of overworn clichés about virtuous cycles. Maybe this is worth a try. Striving to exceed expectations and demonstrably do so really do circle high above grounded talk of how difficult everything is.

We're here to help! Use what you've got, the work of six experts supported by the people you work for.

Please no-one opine in an answer or comment, seriously or coyly, about how manual forum trawling and belaboured, repetitive, condescending rhetoric is somehow a more real or better dialogue than one supported by automation, visualisation, and distraction reduction.

@hansa / @HansA:

Is there a way to be more involved in aspects of device (software) intetaction design, so that when a new device or OS iteration comes out we can know better whether and why we want to buy, and so that we can know if and how our contributions may be improving things?

Wrt the overview info, examples, use cases and interaction-mapping directed graphs made available on this forum would help its users to file questions visually, in a way that would let the interaction design staff and code editing developers zero in more exactly on the issues raised and give better feedback, more clearly and faster.

Moreover, Duplicate mitigation could become part of the Question submission process. The Question's relation to the UI and UE for a specific use case or context and a related chosen step therein will help clarify similar and similarly-positioned issues, and allow Questions likely to be marked Duplicate to instead be automatically linked, and even combine votes for action to amend the common interaction step.

As I perceive it, that would be a better form of online community outreach, better for all related development work flows and better for marketing and sales. It is not just an issue of filing this under forum improvement. There are knock-on effects and all kinds of overworn clichés about virtuous cycles. Maybe this is worth a try. Striving to exceed expectations and demonstrably do so really do circle high above grounded talk of how difficult everything is.

We're here to help! Use what you've got, the work of six experts supported by the people you work for.for and by the people who bought a phone and think your work should be mostly directed by them.

Please no-one opine in an answer or comment, seriously or coyly, about how manual forum trawling and belaboured, repetitive, condescending rhetoric is somehow a more real or better dialogue than one supported by automation, visualisation, and distraction reduction.

@hansa / @HansA:

Is there a way to be more involved in aspects of device (software) intetaction interaction design, so that when a new device or OS iteration comes out we can know better whether and why we want to buy, and so that we can know if and how our contributions may be improving things?

Wrt the overview info, examples, use cases and interaction-mapping directed graphs made available on this forum would help its users to file questions visually, in a way that would let the interaction design staff and code editing developers zero in more exactly on the issues raised and give better feedback, more clearly and faster.

Moreover, Duplicate mitigation could become part of the Question submission process. The Question's relation to the UI and UE for a specific use case or context and a related chosen step therein will help clarify similar and similarly-positioned issues, and allow Questions likely to be marked Duplicate to instead be automatically linked, and even combine votes for action to amend the common interaction step.

As I perceive it, that would be a better form of online community outreach, better for all related development work flows and better for marketing and sales. It is not just an issue of filing this under forum improvement. There are knock-on effects and all kinds of overworn clichés about virtuous cycles. Maybe this is worth a try. Striving to exceed expectations and demonstrably do so really do circle high above grounded talk of how difficult everything is.

We're here to help! Use what you've got, the work of six experts supported by the people you work for and by the people who bought a phone and think your work should be mostly directed by them.

Please no-one opine in an answer or comment, seriously or coyly, about how manual forum trawling and belaboured, repetitive, condescending rhetoric is somehow a more real or better dialogue than one supported by automation, visualisation, and distraction reduction.

@hansa / @HansA:

Is there a way to be more involved in aspects of device (software) interaction design, so that when a new device or OS iteration comes out we can know better whether and why we want to buy, and so that we can know if and how our contributions may be improving things?

Wrt the overview info, examples, use cases and interaction-mapping directed graphs made available on this forum would help its users to file questions visually, in a way that would let the interaction design staff and code editing developers zero in more exactly on the issues raised and give better feedback, more clearly and faster.

Moreover, Duplicate mitigation could become part of the Question submission process. The Question's relation to the UI and UE for a specific use case or context and a related chosen step therein will help clarify similar and similarly-positioned issues, and allow Questions likely to be marked Duplicate to instead be automatically linked, and even combine votes for action to amend the common interaction step.

As I perceive it, that would be a better form of online community outreach, better for all related development work flows and better for marketing and sales. It is not just an issue of filing this under forum improvement. There are knock-on effects and all kinds of overworn clichés about virtuous cycles. Maybe this is worth a try. Striving to exceed expectations and demonstrably do so really do circle high above grounded talk of how difficult everything is.

We're here to help! Use what you've got, the work of six experts supported by the people you work for and by the people who bought a phone and think your work should be mostly directed by them.

Please no-one opine in an answer or comment, seriously or coyly, about how manual forum trawling and belaboured, repetitive, condescending rhetoric is somehow a more real or better dialogue than one supported by automation, visualisation, and distraction reduction.

@hansa / @HansA:

Is there a way to be more involved in aspects of device (software) interaction design, so that when a new device or OS iteration comes out we can know better whether and why we want to buy, and so that we can know if and how our contributions may be improving things?

Wrt the overview info, examples, use cases and interaction-mapping directed graphs made available on this forum would help its users to file questions visually, in a way that would let the interaction design staff and code editing developers zero in more exactly on the issues raised and give better feedback, more clearly and faster.

Moreover, Duplicate mitigation could become part of the Question submission process. The Question's relation to the UI and UE for a specific use case or context and a related chosen step therein will help clarify similar and similarly-positioned issues, and allow Questions likely to be marked Duplicate to instead be automatically linked, and even combine votes for action to amend the common interaction step.

As I perceive it, that would be a better form of online community outreach, better for all related development work flows and better for marketing and sales. It is not just an issue of filing this under forum improvement. There are knock-on effects and all kinds of overworn clichés about virtuous cycles. Maybe this is worth a try. Striving to exceed expectations and demonstrably do so really do circle high above grounded talk of how difficult everything is.

We're here to help! Use what you've got, the work of six experts supported by the people you work for and by the people who bought a phone and think your work should be mostly directed by them.

Please no-one opine in an answer or comment, seriously or coyly, about how manual forum trawling and belaboured, repetitive, condescending rhetoric is somehow a more real or better dialogue than one supported by automation, visualisation, and distraction reduction.