Rather than removing the back button (which personally I think is a bad idea), I think a better approach would be to set it up in such a way that there is nothing to go back to.
You could do this as follows:
- Create a Single Row table, and make this the source of a tab that is the only tab visible to non-registered users.
- Add a “Get Part of URL” column. Configure it to take the
idparameter from the Link to the Current screen. - Publish your App, open it as a non-registered user, and capture the URL of the screen that sits on your single row table.
- Now construct a URL, appending an
idparameter on the end, whereidis the RowID of the row in the other table that you want to expose. So you should wind up with something that looks like the following:https://my.glide.page/dl/dcc150?id=SPg1jOB8QVmnvqsU0L1P5w(This is the URL pattern that you will give to non-registered users). - In the single row table, create a single relation column that matches the extracted RowID with the RowID in the other table (where your content is).
- Add a number of lookup columns that fetch the values you need via the single relation
- Display these on the screen.
Using the above approach, you should find that there will be no back button displayed on mobile, because it is a top level screen, and hence there is nothing to go back to.
I have tested this solution, and it works as described. Please note however, that it will only work in the published App. It will not work in the builder.
Also note that the caveat that Jeff Hager pointed out about data security still applies.