this post was submitted on 10 Jun 2026
21 points (95.7% liked)
Open Source
47272 readers
54 users here now
All about open source! Feel free to ask questions, and share news, and interesting stuff!
Useful Links
- Open Source Initiative
- Free Software Foundation
- Electronic Frontier Foundation
- Software Freedom Conservancy
- It's FOSS
- Android FOSS Apps Megathread
Rules
- Posts must be relevant to the open source ideology
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
- !libre_culture@lemmy.ml
- !libre_software@lemmy.ml
- !libre_hardware@lemmy.ml
- !linux@lemmy.ml
- !technology@lemmy.ml
Community icon from opensource.org, but we are not affiliated with them.
founded 6 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Can you help me understand the purpose of this? Usually I want PWAs running in my preferred browser.
I prefer to have PWAs not in my preferred browser and others would as well.
Okay, but why?
For some web apps, I want it to look and behave like an "app", without the clutter of the extra menus that a browser has.
For others, I want it to have the protections and capabilities (ex. adblocking and extensions) that the browser has
That's exactly what a normal PWA does. It's not what this app does, it adds menus on top of your PWA.
That's also what a normal PWA does.
It might be that this one can take non-PWA websites and make them behave like proper PWAs?