This apparently "trivial." One obvious thing we'll probably need an in-app back button of some kind but I've never made a PWA so maybe other stuff is necessary.
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!
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
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.
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.
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 :)
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.
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.
I updated the README of the repo to let people know everything is basically a bounty but spelling it out probably helps ... I need to send you sats too for your recent PRs.
We pay sats for PRs. Sats will be proportional to the impact of the PR. If there's something you'd like to work on, suggest how much you'd do it for on the issue. If there's something you'd like to work on that isn't already an issue, whether its a bug fix or a new feature, create one.
nice
but spelling it out probably helps
Yeah, definitely. I think generally people don't expect to get paid for PRs and it's weird to ask for payment. If you already mention it yourself, it takes away a lot of the inhibition. It will probably take some time until v4v becomes the norm
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).