Wow ! So smart and useful! Thank you for sharing.
Show HN: Using Google Sheets as the back end/APIs of your app
101–110 of 171 posts
Re: Show HN: Using Google Sheets as the back end/APIs of your app
#102Great job having fun and practicing making a company. Love it. Keep going! I remember using this one https://www.sheetgo.com/ back when they were starting. Fun to watch them grow!
Good luck!
Re: Show HN: Using Google Sheets as the back end/APIs of your app
#1032 Google Sheets backend stories: - Needed to manage vocab learning content for 60 world languages, mostly being updated by a handful of university students and a bunch of remote volunteers. Google Sheets was our source of truth, with a nightly sync into MariaDB. We even wrote some callable scripts that could detect ambiguities and other common issues. Saved us a ton of tooling effort, and stakeholders found it cool t…
what Figma plug-in?
Re: Show HN: Using Google Sheets as the back end/APIs of your app
#104Great job having fun and practicing making a company. Love it. Keep going! I remember using this one https://www.sheetgo.com/ back when they were starting. Fun to watch them grow! Good luck!
Actually it was https://sheetsu.com/ ! :)
Good memories
Re: Show HN: Using Google Sheets as the back end/APIs of your app
#105You don't actaully need any fancy wrapping.. just open https://script.google.com/ you can already access all google's APIs + you will be able to integrate your sheets with your gmail (send email), calendar (you can modify the calendar when the sheet get changes), create pages, allow inputs from form and etc..) The problem with that is the sheet will not have any .. transaction based ops like a real database so for ex…
Every time someone makes a simple solution for a problem on this website someone else points out that a much more complicated option already exists.
I'd like to nominate this comment for the HN Hall of Fame
Re: Show HN: Using Google Sheets as the back end/APIs of your app
#106to use zerosheets, you need to allow it: See, edit, create, and delete *all* your Google Sheets spreadsheets.
Re: Show HN: Using Google Sheets as the back end/APIs of your app
#107to use zerosheets, you need to allow it: See, edit, create, and delete *all* your Google Sheets spreadsheets.
Seems like you'd want a special purpose Google account then, rather than your personal one with your financial spreadsheets in it.
Re: Show HN: Using Google Sheets as the back end/APIs of your app
#108I recently made a full web app using only AppsScript and Google Sheets as the database, and wrote about it here [0], and open sourced it here [1]. It was a novel experience, but I felt particularly compelled by the idea of having a data store than non-devs can easily interact with while having a web app in front of it that didn't require a server to be set up. But, AppsScript is too slow for this kinda thing to be a…
> having a data store than non-devs can easily interact with while having a web app in front of it that didn't require a server to be set up Isn't this one of the use cases for Airtable?
[dead]
Re: Show HN: Using Google Sheets as the back end/APIs of your app
#109I'm surprised no one's posted Spread API yet: https://spreadapi.roombelt.com/
It's a free Google Sheets / Apps Script you just paste to your sheet, and it turns the sheet into a full CRUD. It's kind of rate limited though but completely free!
Edit: I've thought about creating a company around Sheets before, and the problem is that once you get to the "willing to pay" stage, you also kind of outgrow Sheets. I'd rather migrate to Turso, Cloudflare D1, or Pocketbase instead of staying with Sheets or SpreadAPI, because of the limitations.
Re: Show HN: Using Google Sheets as the back end/APIs of your app
#110Is the Google Sheets API rate limit open enough for actual production use? I thought it was pretty restrictive, no more than 60 writes per minute, but I'm not sure about the reads restrictions.
Yes. I used Google sheets as a database to build a website and ran into this issue. The worse part is, if you come across the limit there’s not much you can do but wait or rate limit. Another problem I had is an API change one year in. I would not use Google Sheets again. Maybe I’d try Airtable, Notion, or some other similar platform where the API access is more of a priority to the company.
For reading sheets, it's better to use the "share as CSV" option since that gets cached pretty well w/o limits