When you get other people working on your app/s, you need to think about how to get code from one place into another.
Glide does NOT offer any form of design refreshing from another template, nor can you copy tabs or other pieces between apps, and within apps you can copy tabs (thanks!) and UX components, but you cannot copy columns (computed, etc), and you cannot copy between data tables.
Some people complain… others do not like the answer ‘no’
So what I have done is have some contractors work on a copy of the app, then walk me through how to bring their code changes into my live app. More recently I am experimenting with having someone actually work in the live app (checking I do not need it … as we kick each other out).
Within the app, you can actually do a lot in a way that does not interrupt end users. I duplicate a tab and work on improving that tab… and when it is ready, I change the routing between the tabs via buttons and compound actions. This allows me to work on live, with live data, whilst not disturbing people.
BUT not ideal… so I am looking forward to Glide changing the way we push out design changes.
In terms of Glide Tables, I have my master table, TestFlow. This is shared between the User and the Agent App. I copy in data I need from user Profiles (CollectUser in my case) or from Agents, or from other parts of the app so I can reference the data I need in TestFlow. If the column is needed on both sides, I have to think about usc (can only work if you have a button that moves the user value into a shared column), about the time it takes for the data to go from device, to server, and then push to the device, and what values I might need in one place and not the other.
Considering how it is built, it is pretty slick, and likely only to get better.
Now the way I did it with GS might have been potentially more functional, but it would have collapsed totally.