| This is a great concept! I'm not surprised to see you getting flak for building on Airtable, but as a "real developer" leaning heavily on low/no code lately I wanted to share how well it's worked for our open source team over the last few months. In terms of scale, it has supported dozens of editors, hundreds of public submissions, and several thousand rows of data. We have also successfully scripted a number of use cases using the API for workflows that can be automated. The biggest benefits from my perspective are: 1. Minimal overhead for schema changes. We have been able to overhaul our schema on more than one occasion with no intervention from developers up front. We let the content team shape the data in a way that makes sense then update our client code to fit 2. The UI is obvious to technical and non-technical users alike. Who doesn't know how to use a spreadsheet? 3. No-code workflows are trivial to prototype and launch with blocks and forms. Is it going to work forever? No, we're already moving the more stable+dynamic tables into a SQL database. But I'm sure that we've saved dozens if not hundreds of hours of time in our frequent iterations these first few months. I'm sure we'll keep using Airtable for new features. [0]: https://climatescape.org/
[1]: https://github.com/climatescape/climatescape.org |
If you want more: https://linkedin.com/in/zackshapiro