41–50 of 238 posts
Why lock down to a nocode tool instead of just hacking together a simple html5 page? Ai assistants have speed up the prototype workflow for doing less code/design.
Let go of your complex solutions. Spreadsheets were the right answer all along.
I use Notion databases for this. They're essentially spreadsheets with customizable table, list, kanban views, and each row gets its own wiki-style page in addition to the structured data. So it's nice for lists of books or movies or games, where you have some metadata but you also might want to take notes on it when you read/watch/play. It works pretty well for this purpose, but I also could probably make Obsidian o…
A little know Google product is called Tables[0]. Very similar to what you’re describing. Another is AppSheet[1] for a more drag and drop application builder. [0]: https://tables.area120.google.com/ [1]: https://about.appsheet.com/home/
Important update: The Beta program is now closed Tables is no longer accepting new users for its Beta program
I use Notion databases for this. They're essentially spreadsheets with customizable table, list, kanban views, and each row gets its own wiki-style page in addition to the structured data. So it's nice for lists of books or movies or games, where you have some metadata but you also might want to take notes on it when you read/watch/play. It works pretty well for this purpose, but I also could probably make Obsidian o…
Earlier quoted context omitted.
A little know Google product is called Tables[0]. Very similar to what you’re describing. Another is AppSheet[1] for a more drag and drop application builder. [0]: https://tables.area120.google.com/ [1]: https://about.appsheet.com/home/
From the Tables page: Important update: The Beta program is now closed Tables is no longer accepting new users for its Beta program
> Table’s features and capabilities are now integrated into AppSheet, our no-code platform that blah blah blah
Seems like a usual Google product in that if you use it, you'll be forced to migrate all your data/workflows to some shiny new thing every few years.
I haven't worked on these types of projects for nearly two years now. Folks I know use Retool or Softr with an API connectivity platform like Portable, Pipedream, or Zapier. If you're staring at a spreadsheet on a daily basis, the next step should be looking into an app builder combined with an API connection platform.
I use Notion databases for this. They're essentially spreadsheets with customizable table, list, kanban views, and each row gets its own wiki-style page in addition to the structured data. So it's nice for lists of books or movies or games, where you have some metadata but you also might want to take notes on it when you read/watch/play. It works pretty well for this purpose, but I also could probably make Obsidian o…
I use Notion databases for this. They're essentially spreadsheets with customizable table, list, kanban views, and each row gets its own wiki-style page in addition to the structured data. So it's nice for lists of books or movies or games, where you have some metadata but you also might want to take notes on it when you read/watch/play. It works pretty well for this purpose, but I also could probably make Obsidian o…
I badly, badly wish Obsidian had some kind of database/spreadsheet feature. I'm limping along with LibreOffice spreadsheets for privacy, but it's a pain having my notes in two different formats. And I miss grep.
I got 1 sheet to work well with like 1k rows and thought woohoo this is great! So I went all-in, put 25k rows in and Google pooped the bed. It gave errors all the time, rows and columns were funky. API issues galore.
SQLite however handled 25k rows without any errors, always rock solid.
I gave up. Overall a terrible experience once I got past 1k rows. I'm glad it's worked well for you.
I only had like 10 columns, so it wasn't like massive amounts of data. I was linking to a file out in Google Drive and that was where most of my issues were. Google drive's API was 99.99% completely useless.
My takeaway from the experience was, Google proclaims they have an API, but it seems more like nobody tests it or cares about it. Perhaps it's malicious compliance, they have it because they have to have an API, but not because they expect anyone to actually use it.
Perhaps I'm just not cool enough for Google.