Hello everyone,
I have been working on building and designing systems using Airtable for a while now, and I have developed a preference for creating different connecting bases. For example, I typically build a CRM System Base and a Project Management Base that have synchronized tables but operate independently.
My main objective has been to keep the bases as user-friendly as possible by minimizing the number of tables and allowing independent access for contributors. This approach has worked well, although it does have some drawbacks.
Lately, I have been focusing more on building interfaces, and this has helped mitigate the issue of having too many tables. Users no longer see or care about the number of tables present, which allows me to design the base structure purely based on functionality, without having to prioritize usability as much.
I am curious to hear other perspectives and thoughts on this topic, as I am currently leaning towards using one larger base in most cases.
Thank you.
