Comment

Comment by henryfjordan

Cool! I'll add one more thought that I think might be particularly useful

> Granular permissions not only at row level but field level too. You can share parts of data with others for editing or have it view-only with ability for commenting and accepting suggestions

In my org (and I suspect many), many of the Sales/Operations people maintain Google Sheets with links into our internal apps. Generally it's TODO lists or other little organizational/workflow type stuff

What I think makes Airtable so powerful is that foreign-keys are first class. You can create a table and include references to rows from other tables. This allows the end user to create tables to support their workflows directly in the same tool they use to manage the data, and means I don't have to build that same functionality into the CRUD app (and until you're deep in a workflow it's hard to get it perfect, so there's always back-and-forth).

A good permission system would allow me to create a set of "core tables" that I tightly control the schema of, but allow others to still create tables which reference this one.

Discussion

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton