@gsilvapt @adam thanks for sharing your ideas.
there should be scope for some kind of ‘progressive enhancement’-style approach to this, allowing to address both simpler scenarios where no view-oriented description of the data is available, to more complex scenarios such as the one sketched by @adam.
in a way, as i read more about the various tools and strategies already out there or being discussed, it seems to me that the original ‘intents’ idea could roughly translate to a lightweight system to match metadata exposed by (or inferrable from) data packages, and capabilities exposed by frontend apps - roughly corresponding to Intent objects and Intent filters in the Android’s Intents system: by default this could just lead e.g. to ReclineJS or to Vega/Vega Lite views, whilst allowing more ad-hoc matches where metadata is available on either side (data packages or frontend apps).
i’ll try to add a brief spec and some rough code on a public repo to test whether this makes sense 