tried it, sign in and ssl doesn't work.
same
Show HN: Using Google Sheets as the back end/APIs of your app
31–40 of 171 posts
Re: Show HN: Using Google Sheets as the back end/APIs of your app
#32Reading the documentation, I was expecting more tbh.
As I found out there is no way to customize the API. The response is always a JSON dump of that google Sheet.
Re: Show HN: Using Google Sheets as the back end/APIs of your app
#33I used to use a Google Sheet to drive a restaurant website's menu page. It was perfect. The restaurant could update the spreadsheet whenever something changed, and it'd instantly be reflected on the web. If they ever messed something up, they could just revert.
Re: Show HN: Using Google Sheets as the back end/APIs of your app
#34Re: Show HN: Using Google Sheets as the back end/APIs of your app
#35This looks great. I tried doing it myself a while back using existing client libraries for Python and was surprised how annoying the setup is, like the spreadsheet auth in particular.
I'm also surprised Google hasn't tried to kill this use-case. That's my main hesitation for using it on anything semi-serious.
Re: Show HN: Using Google Sheets as the back end/APIs of your app
#36Didn't https://www.glideapps.com famously start with Google Sheets backend?
Re: Show HN: Using Google Sheets as the back end/APIs of your app
#37Are Fortune, The Weather Channel, Fast Company, and National Geographic really your customers?
Re: Show HN: Using Google Sheets as the back end/APIs of your app
#38https://github.com/benborgers/opensheet#readme Is the best and simplest tool for turning Google Sheets accessible quickly.
Re: Show HN: Using Google Sheets as the back end/APIs of your app
#39Didn't https://www.glideapps.com famously start with Google Sheets backend?
Levels.fyi as well: https://www.levels.fyi/blog/scaling-to-millions-with-google-...
Re: Show HN: Using Google Sheets as the back end/APIs of your app
#40Earlier quoted context omitted.
Couldn't you cache the reads? Not many usages really require real-time from their data store.
Do you really want to deal with caching logic for what should be a simple API call? Sounds like a convincing argument to use whatever this product is.
client = (APIcall) => redis.get(sha1(APIcall)) || { res = api(APIcall); redis.set(sha1(APIcall),res) return res }
Not that hard. Like 10 lines of code to get a decentish cache going.