We have developed an editor add-on which has already been approved and published publicly on the Google Marketplace, but we're still not sure of eventual costs that may originate from its adoption and usage.
Our understanding is that a published add-on acts much like a server instance in a client-server situation. In such a scenario, every time a user installs and enables this add-on on a document of their own, we believe that this document will then act as a new client/consumer of this server instance -- very much like a browser accessing a web server or a backend API.
If such an assumption is correct, we would like confirmation if it would also be correct to say that the add-on will never be "installed per se at the user's side", and will always run under our worksapce account. Is this assumption correct?
If previous assumptions are correct, I guess it is then reasonable to think that any and all costs incurred from usage derived from all of its users would have to be sustained by ourselves. Is this reasoning correct?
Thanks.
LinkedIn
Twitter
