Since finding Airtable, we have been actively creating many apps to digitise our businesses. So far we pretty much have a base for each app. Some apps are for a specific company of ours, whilst some like HR and Tax/Assets are apps that apply to more than one of our companies. We use Stacker as the interface for most users.
We have come to realise that there are some data that might make sense to be thier own base(s). Contact (suppliers, customers, staff, everyone any company comes into a transaction with) is one example. Products is another (things that all companies buys, and in some cases, maintain as assets).
So, I would like some advice if it does make sense to create these two data sets as their own Bases and sync one-way to any destination base that needs/interacts with them. It would presumably mean that Contacts and Products become it’s own separate app, and anytime a new Contact or Product interacts with any of the other apps, a new record needs to first be created in the Contacts/Product app.
Is this the corect approach? Would it get too cumbersone in practise to have to add a new product to be purchased in any of the company(s) apps, first in the Contacts/Product App and then proceed in the operating apps? Or does a multi-sync base works better? Or that’s actually for other use cases altogether.
Any advise from all experinced developers in this community is greatly appreciated.