Great introduction to Google Apps Script and an interesting real use case. Ultradox looks like quite a powerful tool for anyone using G Suite or interesting on what you may built on Apps Script.
He very conveniently jumps past the aches and pains that come from deploying as a Sheets add-on. It's not just add some screenshots and other details. It is add screenshots and security keys, and project IDs, and obscure manifest files, and project IDs.... All of which doesn't work because it's trying to make a chrome extension that doesn't make sense.
I've been looking everywhere for a solid tutorial on how to deploy a sheets add-on just within my domain. The process is a hopeless spaghetti pile as you say of security keys, project IDs, etc. Do you know of a tutorial or guide that will actually guide through the process?
I love sheets/excel but writing single line formulas always seemed so much more tedious and limited than it needed to be. Not to mention it was not easy to debug or test new things. Most times even though I have to write a bit more I still use AppScript just because it's easier to read, comment, and debug. Do beware though, it's really fast on the server (gs code files) and fast on the client (js embedded in html) but it will be really slow to make requests (google.script.run calls) between them. Takes some optimization but I can usually keep these calls to under a second. That being said templating data into your html before you serve it and wetting the page goes a long way. Usually more code but can really help with performance.
The term "serverless", as noted in the video, might be called "zero provisioning." Thank you for explaining the use of the term within this context. I have found the use of the term "serverless", in this context, to be something that makes no sense, and is therefore confusing. My initial thought was, "It must run in the browser, on the 'clients' computer" I mean, if it's "serverless" then there must not be a server involved. Right? Of course Apps Script doesn't run in the browser. Using the term "serverless" to describe a service that runs on the server, is confusing at best. Promoting something as "serverless" seems to be a mute point to me. Unless you, or your organization, buy servers, and maintain them, then what you are using is already "serverless."
Like the presenter from google a lot. He emphasizes all the key words so we understand all the important ideas without confusion !!
Great introduction to Google Apps Script and an interesting real use case. Ultradox looks like quite a powerful tool for anyone using G Suite or interesting on what you may built on Apps Script.
He very conveniently jumps past the aches and pains that come from deploying as a Sheets add-on. It's not just add some screenshots and other details. It is add screenshots and security keys, and project IDs, and obscure manifest files, and project IDs.... All of which doesn't work because it's trying to make a chrome extension that doesn't make sense.
I've been looking everywhere for a solid tutorial on how to deploy a sheets add-on just within my domain. The process is a hopeless spaghetti pile as you say of security keys, project IDs, etc. Do you know of a tutorial or guide that will actually guide through the process?
I love sheets/excel but writing single line formulas always seemed so much more tedious and limited than it needed to be. Not to mention it was not easy to debug or test new things. Most times even though I have to write a bit more I still use AppScript just because it's easier to read, comment, and debug.
Do beware though, it's really fast on the server (gs code files) and fast on the client (js embedded in html) but it will be really slow to make requests (google.script.run calls) between them.
Takes some optimization but I can usually keep these calls to under a second. That being said templating data into your html before you serve it and wetting the page goes a long way. Usually more code but can really help with performance.
This is simply an ad for Ultradox. It would've been more useful to have a demo to "build" an add-on as the title misleadingly suggests.
The term "serverless", as noted in the video, might be called "zero provisioning." Thank you for explaining the use of the term within this context. I have found the use of the term "serverless", in this context, to be something that makes no sense, and is therefore confusing. My initial thought was, "It must run in the browser, on the 'clients' computer" I mean, if it's "serverless" then there must not be a server involved. Right? Of course Apps Script doesn't run in the browser. Using the term "serverless" to describe a service that runs on the server, is confusing at best. Promoting something as "serverless" seems to be a mute point to me. Unless you, or your organization, buy servers, and maintain them, then what you are using is already "serverless."
Is it free to publish a private addon ?
first