# Removing default 'back' navigation on mobile

**URL:** <https://community.glideapps.com/t/removing-default-back-navigation-on-mobile/82310>\
**Category:** Feature Requests\
**Created:** [June 7, 2025, 8:44pm UTC](https://community.glideapps.com/t/removing-default-back-navigation-on-mobile/82310 "2025-06-07T20:44:52Z")\
**Posts on this page:** 9\
**Page:** 1

<div class="post-metadata">

**Author:** ![Ruslan\_Raspopov](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/ruslan_raspopov/32/82885_2.png) [@Ruslan\_Raspopov](https://community.glideapps.com/u/Ruslan_Raspopov)\
**Post date:** [June 7, 2025, 8:44pm UTC](https://community.glideapps.com/t/removing-default-back-navigation-on-mobile/82310/1 "2025-06-07T20:44:52Z")

</div>

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.

 ![Screenshot 2025-06-07 at 4.43.30 PM](https://us1.discourse-cdn.com/flex002/uploads/glideapps/original/3X/f/f/ff733cd5f7815ae8595417572c453ba7dccbc448.jpeg)

---

<div class="post-metadata">

**Author:** ![Hassan\_Nadeem](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/hassan_nadeem/32/72956_2.png) [@Hassan\_Nadeem](https://community.glideapps.com/u/Hassan_Nadeem)\
**Post date:** [June 7, 2025, 11:10pm UTC](https://community.glideapps.com/t/removing-default-back-navigation-on-mobile/82310/2 "2025-06-07T23:10:18Z")

</div>

I guess you can hide the button through CSS, but I wouldn’t want it to be removed. How would users go back then?

---

<div class="post-metadata">

**Author:** ![MaximeBaker](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/maximebaker/32/80877_2.png) [@MaximeBaker](https://community.glideapps.com/u/MaximeBaker)\
**Post date:** [June 8, 2025, 11:50am UTC](https://community.glideapps.com/t/removing-default-back-navigation-on-mobile/82310/3 "2025-06-08T11:50:38Z")

</div>

I agree with a native way of doing it.

---

<div class="post-metadata">

**Author:** ![Ruslan\_Raspopov](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/ruslan_raspopov/32/82885_2.png) [@Ruslan\_Raspopov](https://community.glideapps.com/u/Ruslan_Raspopov)\
**Post date:** [June 8, 2025, 12:45pm UTC](https://community.glideapps.com/t/removing-default-back-navigation-on-mobile/82310/4 "2025-06-08T12:45:37Z")

</div>

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)

---

<div class="post-metadata">

**Author:** ![Darren\_Murphy](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/darren_murphy/32/47326_2.png) [@Darren\_Murphy](https://community.glideapps.com/u/Darren_Murphy)\
**Post date:** [June 8, 2025, 1:11pm UTC](https://community.glideapps.com/t/removing-default-back-navigation-on-mobile/82310/5 "2025-06-08T13:11:23Z")

</div>

> [@Deep link visible to users without an account - does not work](https://community.glideapps.com/t/deep-link-visible-to-users-without-an-account-does-not-work/82309/12):
>
> 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 id parameter from the Link to the Current screen. Publish your App, open it as a non-registered user, and capture the…

---

<div class="post-metadata">

**Author:** ![David\_Gabler](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/david_gabler/32/44332_2.png) [@David\_Gabler](https://community.glideapps.com/u/David_Gabler)\
**Post date:** [June 8, 2025, 1:25pm UTC](https://community.glideapps.com/t/removing-default-back-navigation-on-mobile/82310/6 "2025-06-08T13:25:47Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![Ruslan\_Raspopov](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/ruslan_raspopov/32/82885_2.png) [@Ruslan\_Raspopov](https://community.glideapps.com/u/Ruslan_Raspopov)\
**Post date:** [June 8, 2025, 1:42pm UTC](https://community.glideapps.com/t/removing-default-back-navigation-on-mobile/82310/7 "2025-06-08T13:42:42Z")

</div>

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…

---

<div class="post-metadata">

**Author:** ![Ruslan\_Raspopov](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/ruslan_raspopov/32/82885_2.png) [@Ruslan\_Raspopov](https://community.glideapps.com/u/Ruslan_Raspopov)\
**Post date:** [June 8, 2025, 1:45pm UTC](https://community.glideapps.com/t/removing-default-back-navigation-on-mobile/82310/8 "2025-06-08T13:45:51Z")

</div>

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

---

<div class="post-metadata">

**Author:** ![Darren\_Murphy](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/darren_murphy/32/47326_2.png) [@Darren\_Murphy](https://community.glideapps.com/u/Darren_Murphy)\
**Post date:** [June 8, 2025, 1:50pm UTC](https://community.glideapps.com/t/removing-default-back-navigation-on-mobile/82310/9 "2025-06-08T13:50:11Z")

</div>

> [@Ruslan\_Raspopov](#):
>
> The other issue is that I am limited to 3 tables in the free version

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.
