pull down to refresh
Lack of navigation? I still don't get that argument. Are you using some mobile browser and actually clicking into the forward or back button to navigate? People just swipe back to navigate and PWA supports that just fine. Besides, the only two navigation points are "click story" and "go back home" and the home button at the top solves that.
reply
People just swipe back to navigate
TIL there are gestures for navigation, lol
reply
I do use the gestures occasionally but sometimes I don't. I'm not sure why.
reply
I agree with you, considering the actual standard behaviour and the stacker.news tech savvy target.
But if you think about full accessibility the bottom buttons could be useful, for example for people with reduced/impaired hands movements or using eye/brain/tongue (this is new!) to drive the pointer.
reply
Yes I use the browser nav. I find the swiping inconsistent.
reply
The main feature I want is being able to stay logged in. I’m using private mode in my browser and have a habit of closing tabs.
reply
I think the back gesture today is quite common, I find it very consistent and reliable.
For a really good usability/accessibility (think about people with impaired hands movements) maybe on the first pwa run the app could ask if always on back/forward buttons are preferred, and show them on the bottom.
PWA apps don't have any other options that cannot be exploited on the standard browser view; some are pushed forward (ex. notifications) because are expected in a standalone app.
Don't worry about the bounty, was only a 5 minutes trivial update, I'm happy to gift some time to the project/community :)
reply
standalonecorrect?standalonebefore switching it tobrowserbecause I found the lack of navigation unnerving (and afaict the removal of navigation and chrome was the only "upside" ... which at least subjectively was downside to me).