On Desktop, there is a dedicated Breadcrumbs component that can be added or removed.
However, on mobile there is no way to remove the default back arrow navigation (pointed at with a red arrow). Please give us an option to do so.
I guess you can hide the button through CSS, but I wouldn’t want it to be removed. How would users go back then?
I agree with a native way of doing it.
I have a very specific use case in which I need to remove the said button:
unregistered users who are supposed to land on a particular screen (that is technically implemented as part of a collection, because of Glide limitations), and whom I do not want to be able to navigate to the collection view of the said screen - their only two avaialble options should be to sign up/log in, or close the page altogether.
I was able to remove the breadcrumbs component in the desktop version, but on mobile there is literally no way that back arrow can be removed natively.
I am not that proficient of a user to be editing CSS (hence why I am building with Glide, I know what I want to be happening in the end but I am not a developer)
1 Like
Even if you remove the button from the screen, the user can still hit the physical back button on their device and do it anyway. @Darren_Murphy has the solution.
1 Like
Even if this is the first screen they land on in a browser mode (because what they get is a deep link sent to them in a messenger app), hitting the back button of their phone UI will still bring them back to the home page screen? Is it really how it works? I thought it will simply open the previous web page that they had opened in this specific tab…
That is a very multi-step way to eliminate a single possibility that I am not willing to invest my time into building right now to be honest 
It is not the greatest value-add to the users either. The other issue is that I am limited to 3 tables in the free version I am currently at, and in a true lean fashion I do not want to pay for a paid plan unless I absolutely have to, due to the increase in the amount of users
Where did you get that idea from?
As far as I am aware, there are no limits on the number of tables you can have, on any plan.
Yes, I admit that it’s not a straight forward solution (although, it took me less than 5 minutes to build it out and test it), but what you are trying to do is a little unconventional (in Glide terms), and unconventional needs sometimes require unconventional/novel approaches.
Anyway, totally your choice. I have offered an approach that should meet your needs. You are free to use it or not.
2 Likes