apologies if this has been discussed before - i searched the forum and couldn’t find something similar, but i am aware i am unsure about how this would be framed in general, so i may have missed something that wouldn’t sound related to my eye.
i am familiar with the production/preparation and publishing aspects of frictionless data, but being involved in the development of frontend data visualization apps that could consume data packages, i am wondering if there is prior work in this domain (consumption of data packages).
what i am imagining is a system akin to Android’s ‘intents’ so that (abstracting here from implementation details) a publisher or aggregator of data packages could provide a ‘visualize this dataset’ button, which would then list  possible apps through which the dataset could be visualized.
frontend apps would have to specify somehow what they could accept/what would make sense to try to visualize through them. the app i am currently focusing on (http://pattrn.co/), for example, would only be listed if a dataset provides at least lat, lon, timestamp data, as it provides map-based visualization of events + crossfilter/dimensional charting features. a visualization app that only generates charts ignoring map data would need to specify a minimum set of variables of specific kinds that it would need in order to generate (potentially) meaningful visualizations, and so on.
 Depending on which data visualization apps would make sense to use, according to the data package’s metadata.