I have a weak-spot for Google AppsScript.
Amidst learning to code and finding my way of survival into this post-modern era, over the past decade, I have developed a whole galaxy of custom code and low friction office solutions far beyond the specifics of my own business needs. Into the lands of ‘generic solutions” as a full stack developer, I’m currently building my own full stack node js multi-purpose “boiler plate”, and using it across two or three different projects, each to be launched at their own pace and time.
I started around 2015, using the free Google Workspaces over a couple of specific Google Business accounts. I used Google Sheets as the repository, and AppsScript as my universal office automations stack. Particularly over the past year or two, I’ve made a special place for a pattern or mind-set I developed myself, this being: “Google Docs as an interface”. I found I use them differently from convention.
The now “traditional” cloud based Application Programing Interfaces that revolutionised our lives and the global economy, supporting popular portals, lke Amazon, Youtube or Facebook, have successfully made “computing” more available for a whole generation of communication engineers and self-learned “coders”. PHP, MySQL, NodeJs, React, ORMs, backend, front-end, server-client, processes, data flows, layers, contexts, API interfaces, logic modularity, layering and isolation of “concerns” and now, also LLM, AI, available to “fill in logic gaps” on every step. We are undoubtedly living a new revolution. However, we also face the challenge of keeping up, to a faster pace, and not losing our own ancestral wisdom, human needs, nor running humanity in the process either. We certainly do need to find our place and learn to position ourselves, both professionally and regarding our own personal wellness, in these sophisticated, highly tech demanding new times.
Where I am going is that for many daily small or large, repetitive business or professional needs, a simple Google Doc has nothing to envy over an expensive and complex custom built web application, and you can also use sophisticated and dynamic web application patterns, using a google document as an interface.
Whether it is for taking a simple Minimum Viable Product fast to validate it on the real market, or making internal tools to speed up department procedures - repetitive processes, schedule marketing emails, generate leads, respond to form inputs, generate quotation documents, or payment confirmations - a simple and free Google Workspaces with the right AppsScript framework and patterns, can become a full blown business suite and automations engine today.
Scaling up to a dedicated full-stack web application from there is always easier than starting from a blank page. I’m using Nodejs technology and React based stacks mostly for my own Web Application projects, after exploring options from NestJS and TypeORM as a full backend (https://api.alandalus-experience.com). The line of classical backend/business logic server vs frontend/client interfaces, has specially blurred now with the new hybrid NextJS/NuxtJS environments (https://alanza-coop-v12-44131795481.europe-west1.run.app/). These are exciting new industry breakthroughs, that combined with us all using AI to help us in most of what we do, are also viable in production time and what I call, thought to production friction.
🌐
api.alandalus-experience.com
https://api.alandalus-experience.com
🌐
alanza-coop-v12-44131795481.europe-west1.run.app
https://alanza-coop-v12-44131795481.europe-west1.run.app/
Right now, part of this new artisan HTML website that you are reading right now, is an experiment. Me building a new static HTML template - one I can use or extend to deliver web projects from- while exploring integration options from the right Google Workspace custom AppsScript interface endpoints. It is actually nearly just as good as my NextJS Saas style web application and the rich features I have there, for many business needs, just that it is faster and the environment is steady, ready to build without investing months or thousands, into a fully dedicated WebApplication.
A few months back, around April, I made another Google Docs based script I called specifically that “Dry-AI”, and, well it basically pipelined prompts through documents like a charm, using the documents as a surface, like here but to generate content, not to write it onto a website.
Hasta pronto.