I love it when a simple interface can unlock exponentially greater possibilities / that’s what Sheety does. Google Sheets with Sheety, do I need Airtable any more?
Once you expose your endpoint in client-side JS, anyone could come along and wipe out your data by iterating through record/row IDs? Or write anything they want in there. So this is merely intended for prototyping, or there's another way to protect the data?
@joewardpr this is right Joe! You can create one project for read only (the client) and you can create another project with write access for your admin panel (or whatever), which can be protected with Bearer token or Basic Auth.
Hello Product Hunt!
Earlier this year I launched Sheety V1 which let you do basic reads from your Google Sheet via a JSON API. Since then over 800,000 people have used Sheety, and we serve nearly 80GB of sheets per month – you guys love spreadsheets!
Today I'm launching Sheety V2 which now lets you write to your sheet. You can use standard RESTful interactions: GET, POST, PUT and DELETE. It's also blazing fast: updates happen in realtime. Getting up and running is as simple as connecting your Google account to Sheety, then pasting the spreadsheet URL: schemas and endpoints are generated automatically.
I built Sheety V2 as I spend a lot of my timing prototyping new ideas, and wanted a quicker way of putting together realistic experiences that can be used in the wild!
I can't wait to see what you do with Sheety and would love your feedback :-)
Cheers
I haven't use Sheety, but I have built so many apps pulling data directly from Sheet.
It would be great if Sheety provided caching and fallback in case Sheet is down or rate limited (not sure if it does this today)
Used v1 in production for some time. (Mad! But it worked well). Switching to subscription.
Nice service. Works as advertised and saves a lot of time on prototypes and simple content management!
⭐️⭐️⭐️⭐️⭐️ 5/5
As a designer who sometimes pretends to know how to code, Sheety v1 has been a game changer. Before Sheety, I was reluctant to pursue any project/product idea that involved needing a database of any kind. But then I discovered Sheety, it was way more approachable compared to many other solutions and I was able to turn out an MVP quickly and easily.
Since then I've dug into other more permanent solutions but it's thanks to Sheety for helping me ease into understanding databases. But I will probably start with Sheety again once it's time to turn out a new MVP.
The above probably sounds like a fake testimony, but it is in fact a real one! Pinky promise.
Also, particularly with Sheety V1's website I really appreciated the off-hand sense of humor!
Love it @phillipcaudell, keep up the awesome work!
Scary to have a dependency with another direct dependency which could turn off access anytime.
However definitively cool and interesting. For prototyping and more I’d definitively say it’s worth a shot
@lasserafn Caveat, I don't use Sheety, but I implemented something similar to it, and I felt pretty okay about it knowing I could very easily upload a CSV somewhere else on the cloud to fallback to "just in case".
As a developer, I would love to have the capacity to consume the api as grapqhl. It would be really helpful to have typed queries, known which fields are being consumed (Benefits that with RESTful actually you can't).
Good luck!
@david_sancho might not be exactly what you had in mind, but gatsby has a data source plugin for google docs. Which means that you can source data from a spreadsheet and query it using graphql, since that's the data layer that gatsby uses.
Love the concept, but it being entirely dependant on a 3rd party not shutting down / having downtime would make it next to useless for many (myself included). Have you considered an on-premises version?
And as an extension to that. What contingency have you put in place to ensure anyone wont be cut off from the api should you go out of business?
SparkLoop