pull down to refresh
100k sats \ 16 replies \ @dtonon 4 May 2023 \ on: SN Bounty: turn SN into a PWA meta
This should be what is needed to enable PWA:
https://gist.github.com/dtonon/f8ef73f2a11d26b2cd63d3b0310f7ee6
Wow 100k.. was it you @k00b? Thanks!!
reply
Yep, you put the work and got the conversation started :)
reply
The only difference between this and the current version is that this doesn't live as a tab inside the user's default browser right?
Perhaps this is just an mvp pwa?
reply
Just forked the repo and tested locally, it seems to work:
Would you like to add something?
reply
Just couple UX ideas on top here: #19801
reply
PS: here it's not a simulator, I'm using https://github.com/Genymobile/scrcpy to live stream the smartphone screen so I can grab the screenshots, because otherwise the Firefox menu closes. Check it, it's a nice tool!
reply
The main difference between this and our current manifest is that display is
standalone correct?I "accidentally" made the original SN manifest
standalone before switching it to browser because 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).I wasn't very specific in my bounty so I guess this qualifies. At the very least I'll partially reward it to you.
tbh though my hope was that someone would make a little better use of the PWA options, not realizing that the form factor alone qualifies something as a PWA
reply
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
Exactly.
The PWA version frees up the URL bar and avoids some inconsistencies when it's auto show/hide.
With this tweak, the browser also shows the "Install app" action in the menu.
As @TonyGiorgio stated this is the bare function, then it is possible to add more details like a back button (if needed), a banner to incentive the PWA installation, etc.
reply
That's all a pwa really needs to be to get 90% of what people prefer, which is just to have it look like a dedicated app. You can get all kinds of fancy with it later.
reply