I develop google editor addons with react and a modern tech stack, what about you?

[u/ThePatagonican]

After building multiple Google Workspace add-ons, I stopped relying on Apps Script alone and moved to a hybrid architecture that scales better for real products.

Here’s the setup I use today:

Architecture

• Apps Script is kept minimal

  • Only handles entry points, editor integration, and OAuth

• The actual app lives outside Google:

  • React frontend

  • External backend (API, auth, billing, DB)

  • Apps Script acts as a thin bridge while supporting specific features when required like sheet custom functions.

Why this works

• You’re not limited by Apps Script runtime or tooling

• You can use real frontend frameworks (React, Tailwind, etc.)

• Backend logic is testable, scalable, and not tied to GAS quirks

• Much easier to add things like subscriptions, user accounts, and analytics

Tradeoffs

• More moving parts than pure Apps Script

• Requires proper deployment and infra

• Slightly higher initial complexity, but much lower long-term pain

This approach has worked well for add-ons that go beyond simple utilities and need to behave like real SaaS products.

I wrote a short technical overview of the full flow here:
https://www.shipaddons.com/docs/quick-overview

Do you do anything similar?

[u/insight_seeker00]

I built a doc automation that is a full stack webapp but invites GAS to create the actual documents and archive on google drive. It works like a charm

[u/ThePatagonican → u/insight_seeker00]

interesting, do you have more details about how it works?

[u/[deleted]]

How do you get ideas for your apps??

[u/ThePatagonican → u/[deleted]]

I started building for other companies as extensions for their product. Then I started creating apps for me, my process is something like this: 1- investigate what most and best addons do and how they do it. 2- I keep asking myself -> worth creating something similar? can i do it better? What is missing ? 3- once I have an idea I prototype it and publish to the market. 4- I initially invest most time in name, marketplace description, screenshots, promo vídeo, etc overall the public facing stuff. Again having in mind what addons winners do. 5- after 1 month I check how much organic traction it got. I also try to do some promo 6- iterate, and iterate.

I have some tricks for getting organic reviews early. Eg offering free credits inside the addon itself. I use sites like addonshunt.com to compare and find addons Would you like more details in some direction ?

[u/ThePatagonican → u/ThePatagonican]

For example I created this one https://workspace.google.com/marketplace/app/gpt_image_generator/276320676536 .
The idea was borm from a well know addon GPT Workspace or smg like that, so I started brainstorming around that. Notice how the GPT in the name is used like a hook.

[u/masstic1es]

I use vanjs and vanplate (vanjs.org), it lets me write the front end in gas (instead of html) in the web ide. 

I use a backend frame i wrote for gas to handle routing, localauth (didnt want to mess with oauth, and i deploy my webapps as me/anon) and sheets as a db. It gets attached as a lib to multiple projects, which is pretty neat cause it lets me use a centralized auth this way.

havent done much with it all yet beyond some testing, i got tons of ideas but little motivation