41–50 of 171 posts
Are Fortune, The Weather Channel, Fast Company, and National Geographic really your customers?
Based on OPs description, I wonder if this company was spun up while already doing business with those companies.
Fast efficient easy.
Are Fortune, The Weather Channel, Fast Company, and National Geographic really your customers?
I had this same question. Also, are "developers all over the world" "happily using Zero Sheets"? Based on OPs description, I wonder if this company was spun up while already doing business with those companies.
I'd like to plug PocketBase [0] for a similar use case. Last week I was looking for a place to store random data with API access, and was looking at making a Google Sheets backend, but PocketBase was easy and didn't have a 60 rpm quota [1]. Deploying to a cheap VPS was very easy with CapRover. [0] https://pocketbase.io/ [1] https://developers.google.com/sheets/api/limits
super easy for prototyping and getting the job done, while google sheet as a backend is nice too but I need authentication etc etc
Funny story. Before pivoting my startup to Loom, we were a user testing company named Opentest. Instead of spinning up a DB and creating a dashboard for my co-founders to look at who requested certain user tests, I just dumped everything into a Google Sheet. It was so good. No downtime. Open access. Only 3 people looking/editing, so no conflict. Didn't have to deal with database upgrades or maintenance. I often think…
I've used it for a lot of system data that needs to be modified by a few people at most. With a little bit of careful code and caching (I like validating and syncing to S3) you can easily use it as a crud frontend for important system data.
It also can make great adhoc dashboards - plug into APIs (even private ones if you add in custom Google Scripts code) or push data updates to the sheets. I've had rather large reports auto updated on a schedule with multiple views of the data (pivot tables, queries, lookups, etc). Fully focused customized views into the data needed to solve specific internal problems with really quick delivery times.
Sure, a custom developed option should be substantially better than Google Sheets, but you won't develop it quicker. By the time you actually need something bigger/better, you should be at a place where your needs are better defined and you can afford the resources to develop something better.
Funny story. Before pivoting my startup to Loom, we were a user testing company named Opentest. Instead of spinning up a DB and creating a dashboard for my co-founders to look at who requested certain user tests, I just dumped everything into a Google Sheet. It was so good. No downtime. Open access. Only 3 people looking/editing, so no conflict. Didn't have to deal with database upgrades or maintenance. I often think…
I haven't started yet because (1) I still haven't finished writing up my last user script experience blog post, and (2) I'm terrified of the auth nightmare. It might be easier or harder in the user script context—I am in the context of a web page, so maybe that means I can do a normal oauth flow from there or something?
Funny story. Before pivoting my startup to Loom, we were a user testing company named Opentest. Instead of spinning up a DB and creating a dashboard for my co-founders to look at who requested certain user tests, I just dumped everything into a Google Sheet. It was so good. No downtime. Open access. Only 3 people looking/editing, so no conflict. Didn't have to deal with database upgrades or maintenance. I often think…
its a honor to hear from a loom founder, Ive been using your product for a long time and I love it! 100% onboard on what you said.
Are Fortune, The Weather Channel, Fast Company, and National Geographic really your customers?