[cxr]

There's a lot of stuff in #8, and I'm not sure which part caught your eye, but remember that `postMessage` exists for (serverless) communication between different tabs/windows, even across different origins. That's one way to make "Open in Data Studio" a single-click action:

1. User Alice opens her <file:///Users/Alice/report_from_bob.json.html> in her browser

2. Alice clicks the "Open in Data Studio" button opens <https://local.dataspren.com/import> (or whatever) in a new window/tab

3. Data Studio sends a heartbeat to window.opener

4. Alice's .json.html squirts its own contents to Data Studio

You could consider taking it further from there:

5. Alice works on the copy now loaded in Data Studio

6. As she works, Data Studio squirts the modifications back to the original tab (unless she has closed it)

7. As the modifications flow in, the local copy of report_from_bob.json.html in the original tab shows a banner that the file has been modified in Data Studio (giving her the option to update her copy, save it as a different file name, etc.).

You could also generate a UUID on the Data Studio side at step #3, and even if Alice has closed the original tab, the next time she opens it, it polls Data Studio using that UUID to see if it has any more recent modifications.

PS: Please also be aware that the CSVW group at the W3C has done a ton of work picking up where the IETF left off with RFC 4180, and almost no one knows about it, but it's a treasure trove of info (recommendations, actionable specs, tooling, reference implementations, test suites, etc.) around dealing with CSV and/or data tables in JSON. <https://w3c.github.io/csvw/>

PPS: As you're marketing this, the appropriate buzzword for getting eyeballs is "local-first".