Right now you could share a Mesh file as code, but yes, you'd need to have a way of consuming that code. Right now there's no way of communicating the UI interface; I had envisaged that people would download Mesh separately from the internet.
Embedding Mesh and its dependencies in the file itself is really clever. The file would get a bit bloated but maybe that's OK if:
(a) when the file is consumed by other code, the interface exposed is clear
(b) when the file is opened as a Mesh program, all the user can see is the program shown in the spreadsheet, not Mesh's code.
It is potentially more risky from a security perspective if it is not easy to verify the Mesh source embedded in the file hasn't been changed to be malicious.
Embedding Mesh and its dependencies in the file itself is really clever. The file would get a bit bloated but maybe that's OK if:
(a) when the file is consumed by other code, the interface exposed is clear
(b) when the file is opened as a Mesh program, all the user can see is the program shown in the spreadsheet, not Mesh's code.
It is potentially more risky from a security perspective if it is not easy to verify the Mesh source embedded in the file hasn't been changed to be malicious.