Hacker News new | ask | show | jobs
by Vinnl 456 days ago
As I understand it, two problems are:

1) There's no clear definition of what it's "supposed" to. Not everyone who uses the term PWA wants the same things.

2. Some things are just a lot harder to implement than others.

1 comments

1. if 90% of the people don't want a toolbar in a PWA (I'm being generous about 10% wanting it), it makes sense to not have it

2. It is not harder to implement a button to show the toolbar menu

In all case, it should be (it already is by the spec!) a developer option, not something enforced by the browser.

I have learned a long time ago not to make claims about how hard it is to implement something in other people's projects - I get it wrong often enough about my own.

(Also, I don't think there's a single "PWA spec".)

Firefox's UI can be easily tweaked with CSS. It's trivial, for example, to get rid of all chrome. The real problem is their ideological stance against PWAs.
It's definitely doable to make the bar disappear with a tiny bit of CSS. Did it myself in the past and the Firefox team does it partially for their vertical tabs feature