You know how in Android the back button is sometimes not a back button? It sometimes transforms to a close button (modal, image overlay, keyboard, etc.)
With an app built for iOS, these “close on back” was not working
As a web app, such behaviour will also need to be programmed to work on a browser first. Packaging it for Play Store should not grant that behaviour automatically.
(2) Image overlay
For Voyager, back button for image overlay works in browser.
When opening an image viewer, the web app triggers a browser history change like this:
You know how in Android the back button is sometimes not a back button? It sometimes transforms to a close button (modal, image overlay, keyboard, etc.)
With an app built for iOS, these “close on back” was not working
As a web app, such behaviour will also need to be programmed to work on a browser first. Packaging it for Play Store should not grant that behaviour automatically.
(2) Image overlay For Voyager, back button for image overlay works in browser.
When opening an image viewer, the web app triggers a browser history change like this:
^ notice the extra
#galleryOpenWhen back button is triggered, the web page will listen to a “back” event, and close the image viewer.
(3) Keyboard: Keyboard is a native UI. So triggering “back” will always close the keyboard
(1) Modal / bottom sheet
But… I couldn’t figure out this one yet
Clicking on the “3 dots icon” in a post opens a bottom sheet interface.
Play Store version response to back button properly. But the web app version does not.