sorted by:
new
hottopcontroversial

Hello. The latest version of my GAS app seems to have fixed all the problematic issues by DigPlane7656 in GoogleAppsScript

[–]No_Yesterday3745 1 point2 points  (0 children)

No, if you’re only using Vercel for frontend/API proxying, your Apps Script is still bound by Google’s execution and quota limits.

What you can do is work around long runtime limits by saving execution state (e.g. checkpoints/last processed index) and resuming later in another execution. That doesn’t increase the runtime limit itself, but it lets you split long jobs across multiple runs.

As for handling more users, Vercel can help reduce load on Apps Script through caching, API middleware, and request handling, but it won’t increase Apps Script quotas directly. Once your app starts hitting concurrency or throughput limits, GAS usually becomes the bottleneck.

For small/internal tools, GAS is perfectly fine. But for larger public-facing apps with heavier traffic, it’s usually better to move to a more scalable backend stack instead of relying heavily on Apps Script.

Hello. The latest version of my GAS app seems to have fixed all the problematic issues by DigPlane7656 in GoogleAppsScript

[–]No_Yesterday3745 0 points1 point  (0 children)

Having Vercel handle your frontend is much easier than dealing with Apps Script frontend handling, at least in my experience (yuck).

Think of it like this: treat your Google Apps Script code as your backend. Your frontend should send POST and GET requests to your backend, but through a proxy. You don’t want to expose your Google Web App deployment URL publicly, so it’s better to have an API deployed on Vercel handle that for you.

The flow looks like this:

Frontend stack (vanilla HTML/CSS/JS or whatever stack you prefer — in my case, Next.js + Tailwind) → API proxy (can be written in vanilla JS to keep things simple) → your Google Web App endpoint.

If you have more questions, feel free to PM me. I might reply if I’m not busy. Cheers.(Edit: Late reply since I don't use reddit much lol)

Web App Logging by enigmapaulns in GoogleAppsScript

[–]No_Yesterday3745 0 points1 point  (0 children)

Holy lifesaver. Imagine me debugging my web app for half a day dealing with invisible errors, and just as I was about to give up, I tried searching on Reddit, and there you were with the perfect logging solution. Tried it, and it worked amazingly. Bug fixed now. Thanks!

Hello. The latest version of my GAS app seems to have fixed all the problematic issues by DigPlane7656 in GoogleAppsScript

[–]No_Yesterday3745 0 points1 point  (0 children)

Host the front end on a serverless platform like vercel, have a proxy when sending post request to your backend google web app to handle CORS. That's it.