this post was submitted on 21 Feb 2024
248 points (96.3% liked)

Firefox

20793 readers
7 users here now

/c/firefox

A place to discuss the news and latest developments on the open-source browser Firefox.


Rules

1. Adhere to the instance rules

2. Be kind to one another

3. Communicate in a civil manner


Reporting

If you would like to bring an issue to the moderators attention, please use the "Create Report" feature on the offending comment or post and it will be reviewed as time allows.


founded 5 years ago
MODERATORS
 

Apple has decided to remove Progressive web apps from iOS in EU. If you have a business in the EU or serve EU users via Web App/PWA, we must hear from you in the next 48 hours!

you are viewing a single comment's thread
view the rest of the comments
[–] sjstulga@fosstodon.org 1 points 2 years ago (1 children)

@bloodfart

I could be wrong, but I think you are simply mistaken because there should be absolutely no possible way for the PWA to install a browser engine onto your device? The user can first install the browsers of their choice, separately, and then install PWAs using that browser.

That would be a huge concern and really contradict the entire point and purpose behind PWAs as I understand them... I've been searching but can't find anything like what you say. I'd love to see your source

[–] bloodfart@lemmy.ml 1 points 2 years ago

I dug up my old development backups from that time and I had it backwards, the advice was to read user agent strings and link directly to the version of the browser your pwa was designed for if you saw they weren’t running the “right” one and were worried about it breaking.

So I was mistaken but the reality was weirdly still bad.

I don’t know if that’s still commonplace. Right now it seems like a lot of pwas target chrome because it’s the most popular browser.