Skip to content

Comment on Ask HN: Experience using your user's Google Drive instead of a database?

Comments

I developed a Telegram bot [1] that allows users to save text messages on Google Sheets, including simple text parsing to arrange the content into columns. Upon signup I automatically create a spreadsheet for the user so that they can start using the bot right away, but they can also change it to a personal spreadsheet later. And of course multiple users can add to the same spreadsheet if they know the link. Note that the bot uses a local SQLite for its own data.

Technology-wise it is just a Java app running on my raspberry and using Google's libraries for Drive [2] to create the spreadsheets and the actual Sheet API [3] to modify content. Authentication was a bit hard to figure out mostly because of the poor documentation. Each query to these APIs takes about one second, so it is definitely not suitable if you require low latency on the client's side or lots of concurrent accesses to the same spreadsheet. Not sure about pricing since my bot is not so popular and I am still in the free tier (:

[1] https://t.me/gsheet_notes_bot

[2] https://developers.google.com/drive/api/guides/about-sdk

[3] https://developers.google.com/sheets/api/guides/concepts

I'm doing something similar, but using SpreadAPI (https://spreadapi.roombelt.com/) which is free and uses Google Apps Script for myself.

I use GPTs with it to save ideas / thoughts / notes, but also to parse URLs with lists like "best burgers" and GPTs will just add details to the sheets.

Sheets is GREAT for personal / small group use, but if you're a massive company you'll probably run into limitations quickly (5 API calls/s; 200k cells; monthly limits) etc. but I've never even gotten close.

AboutSource Built by g1lg1l

Hackerly is an independent reader for Hacker News, built on the public HN API. Not affiliated with Y Combinator.