Back button in iOS PWA

Heavens. It works! You have to catch the outermost left side - in a “regular” iOS App you may grab anywhere on the screen to swipe.
Anyway: this seems to be disabled in PWA fullscreen mode:




ahhh this is the problem. I was trying to find it. Is there anyway to go back to the setting via json or some jquery to override it via customizing the html, no meta tags do it. So im assuming this was gone before its just that the old shortcut was saved prior to then

How are users supposed to use the back button when full screen?

1 Like

I had no problem I would just click the old school icon in the upper right. We are talking about the old add to home screen like this right? If so, then I never really cared but there is a way for a bar to pop up isnt there, or use shortcuts like a left swipe? Invision power boards has it on their forums

Left swipe to go back is disabled by Apple in this mode:

We didn’t design Discourse to be used without the browser back-button, so we disabled the feature for now, like Starbucks in the example above.

Android doesn’t have this problem because a back button is permanent in either the OS UI or in the form of a physical back button.

We are always happy to discuss and re-evaluate, but the situation is kinda messy in iOS.


but if it was active before, why not give the option of a checkbox for certain tiers to enable it for their discourse? It worked great before a nd a lot of the people who used it loved it.

Not on the latest Android Oreo though… they are looking at getting rid of those required buttons because a fullscreen “all screen” phone like the iPhone X/XS … is the future :wink:

1 Like

That is a manufacturer specific customization, only in OxygenOS (OnePlus family). It would not be the first time that Android adopts a manufacturer customization, but considering the time a new Android version takes to spread we are talking 3 years to have some adoption.

If they remove I just hope they don’t block it in the place where it’s so needed like Apple did :stuck_out_tongue_winking_eye:

1 Like

What about a back button coded in a theme component? Would something like that suffice for a PWA?

1 Like

Even better if it can detect that is inside an iOS PWA and activates automatically. No idea about how the UI would be…


This sounds like a lot of work to satisfy a very small number. This topic is 10 months old and has garnered all of 28 responses out of 900+ views. People are hardly breaking the door down for it to be implemented.

1 Like

this was already active, I think people realizing that its gone is what triggered it. I have screenshots of it working 8 days ago. It stopped loggin me in and I cannot get back logged into it. Im at the point ill pay 2000 for an app that does it. It looks so much cleaner without it

Old home screen shortcuts would continue to work, and there may be very old discourse installations where it’s still enabled (because they’ve not updated in a very long while) but it has been out of core for some time now.

oh i didnt install discourse app for it, im talking about just hitting the safari add to home screen button

As am I.

The behavior you’re talking about is controlled by the site you bookmark on the homescreen, and PWA has been disabled in tests-passed (the default that everyone deploys) for a while now.


why cant there be a setting that enables us to use it on the backend, I get it that there are features that dont work but that allows us to make it available

Because that setting would be for all users of a site, not on a per-user basis. That means the site they’re typically used to browsing on mobile/desktop loses the ability to go back a page when they misclick, or want to retread their steps, and can only go to home and start over.

All to reclaim this (red arrows):

On that screen size the red arrow marks out around ~100 pixels, or around 4% of the screen height.

Discourse has millions of users globally, this topic has three people asking about reverting a change. No customers are asking for it’s reintroduction for good reason, that kind of crippled UX borders on user-hostile.


right but a lot of the people I can assure you do not add a bookmark to their screen. I am sure the owner of the company or someone with the proper authority can show you how mamny people use the discourse app. Again this is irrelevant. What is relevant that if someone wants to use it without the silly addressbar on the top it is programmable for a simple switch to turn on said such meta tags to shut it down. Matter of fact, you could go a step further and allow customer header code that would be accepted to shut it down

You’re just making more of a case not to implement this - if it’s for an audience of one, to reclaim 4% of the screen height, it’s not worth the development effort.

Look at my screenshot, the address bar collapses as you scroll down, reducing the height by around ~40%. There’s also value in seeing the domain name and SSL icon.