4 ms·

iOS has many private APIs, this one is no different. The fact it's implemented in WebKit is a red herring.

• bigyabai 1y ago
  So when Google creates self-serving APIs in a web browser engine, it's anti-consumer and is killing the free web. But when Apple creates self-serving APIs in a web browser engine, it's just another private entitlement, a red herring and their right as the proprietor of Safari. The lady doth protest too much, methinks.
  • cosmic_cheese 1y ago
    The difference is that Google is by far in a much more dominant position and every dev who leverages Chrome-specific APIs further entrenches that dominance. In the browser space, Apple is the long-trailing runner-up and has far less impact. It appears that this particular API is restricted to embedded webviews, too (doesn’t work in Safari), so it has no bearing on the open web, unlike APIs such as WebUSB in Chrome.
    • deleted 1y ago
      [deleted]
  • ezfe 1y ago
    It's literally not part of the web because it's not available in Safari or WebKit views in applications.
• catsma21 1y ago
  [flagged]