@NigelP wrote:
So far I have assumed each SharePoint List to be an object and so have built an App around that object which does the usual CRUD operations on the list and then have a master App which calls all of these other Apps.
From what you are saying, this is not the way to go.
Am I correct ?
You can absolutely do it that way but will be overwhelmed with apps.
The way PowerApps is setup you can link to many SharePoint lists (or SQL, CDS, Excel etc.) data sources within one single App.
Then in each screen you can choose what to show or not to show by either linking right to your SharePoint data source or using Collections (the better way to go in most cases). Your choice of when a user can update items or not depends on how you want to display the data to them to edit/update/delete.
For example:
We have a note taking section in the app, the first screen the user sees shows every project that notes could be taken into, then once a project is selected they go to a separate screen that shows all the notes for that project, then when a note is clicked it loads into an Edit/Update/Delete screen OR if they choose to make a New note they are taken to a screen to Create.
This happens throughout our primary app in different locations, all linking to different tables/data sources.
Does that help?