No problem I do get what you are saying, but I do think there is some misunderstanding of my suggestion , my suggestion is not creation of a glue app, and not even an app at all.
The whole point is that there isn’t something sitting in the middle (the app posted is just a skeleton to demonstrate the ability)
So in my initial post there was a an example block of code, and all that codes purpose is, is to capture other apps publishing their availability and to bounce back to anyone of the other apps to say, that the published item has been triggered.
Those 10 lines of code, pretty much do all of the interface work, as in right now without any further development (collecting available activities, maintaining them in case of update/add/remove, and send an execute request), and could in theory exist in every app that wanted to publish their availability. My thought process behind it is that this block of code is kept simple and standard (but community designed and agreed) and any app that wants to be able to trigger another app just needs to paste in this block of code, and only 3 more lines (the subscription, the list and the line to execute:
subscribe(location, “appLink”, appLinkHandler)
input “appList”, “enum”, title: “Trigger This App”, required: false, submitOnChange: true, options: appLinkHandler(value: “list”)
appLinkHandler(value: “send”, data: “$appList”)
So if you added those 3 lines of code (copy and paste) plus the event handler block… this could then trigger events to any other applications that have the same code block, but their own handler, which would listen for the appName and unique ID…
Sorry if any of that was not clear from the original post, but thought I should explain better… as I don’t want anyone thinking I’m developing and app to translate between other apps, my idea was to have a small set of code that exists in each app as a common language, not to translate…
EDIT: Sorry for another long post!