Solved A flexible recipient configuration/picker common across devices

There is a need for a much more flexible recipient/device configuration/picker common across devices that would also be optionally available as one runs an action. Currently, for example, when one creates an action, that action has to be associated with a pre-defined device set for one or more devices. However, there needs to be a more flexible way to define these sets by allowing the user to define their own device sets themselves that are shared across devices. Then, when a user creates an action, they can associate it with one of the built-in sets, or one of their sets, or even multi-select different sets or even individually pick devices to use. They would then have the option to save the configuration as a new shared set or keep it as an ad-hock set for that action. There would also be an option to have an action run silently using the pre-configured set or to use the set as the default and to prompt the user when the action is run in order to allow the user to repeat the configuration process before the action is executed.

When an action then prompts the user to confirm the destination devices, the user can then modify the set and even save it as a new set or set it as the ad-hock default for that action, or say that it is a one-time use only, in which case the set is only valid for that single session. In addition to these options, when the user is prompted this way, the dialog should also contain a switch for displaying prompting in the future. This simply configures the action to "not prompt".

Hope this explanation makes sense.

 

I got so used to doing it all in Join that I forgot all about Tasker.