341–350 of 387 posts
I really, really, really wish iOS allowed push notifications through Safari. So many PWA ideas I want to explore are instantly stifled by that omission.
Is there no alternative way?
Earlier quoted context omitted.
Then you're out of step with what users want these days. Nothing wrong with that! But to take an example, when I hit a share button on a page I want to see the native share box, not some hideous iframed monstrosity that only works with Facebook. So I want Web Share. And I don't want to download an entire native app just so that I can receive a push alert when my food order is on the way, a web site works much better…
Slightly off-topic perhaps, because I think you're making a general point, but although you may want the native shared box it only works for Safari users - https://caniuse.com/#search=web%20share%20api - with apparently very little appetite for it from other browser vendors. Maybe its time will come, but I think there are lots of issues with implementation.
Earlier quoted context omitted.
Or you could just trim the URL yourself.
The problem on mobile devices is that URL bar is single-line and has like 30 characters length and , while query string crap is sometimes several hundreds characters long. It's not every ergonomic. But yeah I often copy the URL to "notepad" app before sharing and trim manually.
Earlier quoted context omitted.
Then turn them off. All these things landed because users _do_ use them. I 100% want web share, page visibility, usb, and native file system, for instance, because the browser has become a convenient replacement for a bunch of playgroup/PoC/testbed applications that I might have used 10 years ago.
There are people who want to be spied by social networks to have a pair of free shoes and post pictures of them online It doesn't mean it's the right thing to do for society Browsers have gone far beyond their purpose in an inorganic way It's like if my alarm suddenly started making coffee, toasts, working as remote and the new planned feature was the ability to warm itself up and iron my shirts And it would still be…
For anyone wondering how well supported these features are globally (from caniuse): prefers-color-scheme: 80.85% prefers-reduced-motion: 84.05% Payment Request API: 90.06% Web Share API: 49.25% Push API: 78.57% Service Workers: 94.42% Web/native app install banners: 68.19% Get Installed Related Apps API: Not launched, 0% WebXR: 61.83% Picture-in-Picture: 85.01% Media Session API: 66.31% Chrome Sender API: 64.75% AirP…
Earlier quoted context omitted.
In terms of development effort, maintaining a browser fork that merely disables these features seems pretty easy. If you think users would prefer that, why not make one? I personally don't think it would take off, because I think most user attitudes range from "want these features" to "ambivalence". But if you're so certain, why not try?
Why does it require a fork? Having an advanced settings page with checkboxes for each of these web features seems straightforward and not overly confusing to normal users.
Earlier quoted context omitted.
Share API isn't needed for sharing content, copy and paste worked better than share api and it was around decades ago. About what percent of push notification requests do you accept? I think my percentage is 0, and the number of requests is high tens if not hundreds. I don't trust browser notifications at all. Here's some stats: https://www.businessofapps.com/marketplace/push-notification... Opt-in rates are around 6…
> Share API isn't needed for sharing content, copy and paste worked better than share api and it was around decades ago. Most big websites have different URLs for the same content. When you're sharing a link, you want the canonical URL, which is neutral and universal, not the URL you're currently on, which might have a session ID, user preferences, scroll anchors, etc appended to it. The share button in your browser…
Share button certainly doesn't work better; I find it so undependable that I intentionally avoid it.
Earlier quoted context omitted.
Share API isn't needed for sharing content, copy and paste worked better than share api and it was around decades ago. About what percent of push notification requests do you accept? I think my percentage is 0, and the number of requests is high tens if not hundreds. I don't trust browser notifications at all. Here's some stats: https://www.businessofapps.com/marketplace/push-notification... Opt-in rates are around 6…
You consider them undesirable, but they are a critical feature for many applications. Specifically, chat. More specifically... support agents providing live chat support. (And for that matter, end users interacting via chat appreciate push notifications on reply) Without browser push notifications, there really isn’t a good alternative. The fact that opt in rates are close to 50% is probably a good thing! It means th…
As a user, so many of these I wish did NOT exist. E.g: Push Notifications, Banners, Web Share, Contacts, Page Visibility, Badging. Uncertain about USB, Bluetooth, Locks, Keyboard Lock, and Native File System. I don't want my browser doing those things.
Earlier quoted context omitted.
False. For starters, browsers can only implement sandboxing thanks to the OS facilities, otherwise it would be impossible. And that is modern ones. 5 years ago some browsers were still a security nightmare with not even multiprocess separation.
There's a difference between what features OSes have and which ones they are effectively using. If you ran untrusted native apps with the same level of consideration that people run untrusted web sites, your identity would be stolen every 30 seconds. That is solid empirical evidence of a better security model.
If we wanted to do so, then the "run" operation on an executable would be different.
There is no difference, and in fact, OS have more features and capabilities to make running untrusted code safe.