zlacker

[parent] [thread] 66 comments
1. samwil+(OP)[view] [source] 2023-01-24 11:30:46
If Apple was forced to compete on iOS for the dominant position that Safari holds, it would receive greater investment, add support for vital missing PWA features and potentially as a result grow its desktop market. I believe competition in the long run would break Blinks dominant position, and be better for both consumers and developers.
replies(4): >>microt+t2 >>nine_k+p3 >>dicker+59 >>acdha+nL
2. microt+t2[view] [source] 2023-01-24 11:52:54
>>samwil+(OP)
If Apple was forced to compete

It is not a fair market since the maker of one of the browsers also owns a significant portion of the websites that people use daily. Now Google has to play nice with Safari to some extend, since the don't want to miss out on the lucrative iPhone market. Once Google can offer Chrome on iOS, they will destroy Safari with the same underhanded practices as they did to Firefox (a pattern of subtly breaking Firefox with Google products).

replies(2): >>samwil+13 >>moonch+kt
◧◩
3. samwil+13[view] [source] [discussion] 2023-01-24 11:56:46
>>microt+t2
> Once Google can offer Chrome on iOS, they will destroy Safari with the same underhanded practices

I don't believe that would happen, firstly Apple would fight back, and secondly the competition authorities would take action against Google.

Google is under scrutiny for its behaviour too.

You can't fight or justify anti competitive behaviour with anti competitive behaviour back.

replies(5): >>nliten+a4 >>girvo+G4 >>philli+46 >>snowwr+Qv >>the_ot+UF
4. nine_k+p3[view] [source] 2023-01-24 11:59:49
>>samwil+(OP)
Vital missing PWA features are indeed vital for Apple to stymie PWAs and force all iOS software through App Store which they fully control. PWAs is a territory where the Apple tax (30%) cannot be enforced.
replies(1): >>Terret+Bh
◧◩◪
5. nliten+a4[view] [source] [discussion] 2023-01-24 12:06:03
>>samwil+13
> firstly Apple would fight back

With what?

◧◩◪
6. girvo+G4[view] [source] [discussion] 2023-01-24 12:09:18
>>samwil+13
You have more faith in our competition authorities fairness and approaches to these mega corps than I do, but I hope you’re right and I am wrong.
◧◩◪
7. philli+46[view] [source] [discussion] 2023-01-24 12:19:20
>>samwil+13
The moment iOS is forced to give browser freedom, chrome has won.

It will be a sad day for sure.

replies(3): >>mtomwe+b8 >>rs_rs_+xi >>izacus+Bn
◧◩◪◨
8. mtomwe+b8[view] [source] [discussion] 2023-01-24 12:35:51
>>philli+46
Already passed in the EU. Recommended in Japan, Australia and the UK.

Apple is not the company fighting for the web or browser diversity, they are the ones holding back.

replies(1): >>sbuk+1d
9. dicker+59[view] [source] 2023-01-24 12:41:31
>>samwil+(OP)
"Vital missing PWA features" are really only vital for devs who don't want to do native mobile apps. For the rest of us, they're a yawn.
replies(2): >>postal+SE >>ch4s3+6F
◧◩◪◨⬒
10. sbuk+1d[view] [source] [discussion] 2023-01-24 13:11:03
>>mtomwe+b8
How? Other than Gecko (Firefox), there is just Blink, which is owned and controlled by Google, and full of proprietary extensions that many here like to claim are standards. WebKit is sadly the last hope for an open web. Pushing for Chrome now is like pushing for IE/Trident in the naughties.
replies(3): >>mtomwe+yf >>rvz+gB >>izacus+WC
◧◩◪◨⬒⬓
11. mtomwe+yf[view] [source] [discussion] 2023-01-24 13:28:41
>>sbuk+1d
https://open-web-advocacy.org/walled-gardens-report/#the-chr...
◧◩
12. Terret+Bh[view] [source] [discussion] 2023-01-24 13:41:01
>>nine_k+p3
Sounds like opinion of those who haven't used the many rich home screen web apps available, indistinguishable from an app store app for most users.

Complaining about this is memetic rather than fact based.

◧◩◪◨
13. rs_rs_+xi[view] [source] [discussion] 2023-01-24 13:46:52
>>philli+46
>The moment iOS is forced to give browser freedom, chrome has won.

...because Chrome is a much better browser? That's what you're trying to say?

replies(2): >>snowwr+uw >>pwinns+6m1
◧◩◪◨
14. izacus+Bn[view] [source] [discussion] 2023-01-24 14:12:41
>>philli+46
That is absolute nonsense. IE hasn't won either (despite its dominance), BECAUSE you could choose another browser.

This is why free markets work and command economies don't.

replies(1): >>snowwr+9w
◧◩
15. moonch+kt[view] [source] [discussion] 2023-01-24 14:41:27
>>microt+t2
What are these websites ?

Search - I don't really see a browser specific optimization potential here.

YouTube is probably mostly app based on mobile.

Gmail and other gsuite apps are also app based on mobile.

I'd be surprised if they cared about mobile Safari support in those much or if it played a big factor.

replies(2): >>endemi+hG >>acdha+AI
◧◩◪
16. snowwr+Qv[view] [source] [discussion] 2023-01-24 14:52:50
>>samwil+13
Apple is already fighting back, with Safari.
replies(1): >>super_+cT1
◧◩◪◨⬒
17. snowwr+9w[view] [source] [discussion] 2023-01-24 14:54:41
>>izacus+Bn
The current browser approach on iPhones was created in a free market.

Using the law to force Apple to run Google software would be an example of a command economy.

replies(1): >>izacus+AC
◧◩◪◨⬒
18. snowwr+uw[view] [source] [discussion] 2023-01-24 14:56:36
>>rs_rs_+xi
Chrome will become the better browser for Google services, because Google will intentionally degrade them on other browsers.

This is not theoretical, the playbook is obvious and has been run before, by Microsoft.

replies(3): >>izacus+eD >>saiya-+yT >>girvo+5N2
◧◩◪◨⬒⬓
19. rvz+gB[view] [source] [discussion] 2023-01-24 15:18:35
>>sbuk+1d
Firefox had its chance to push back again the Chrome dominance. It survived against IE and became the dominant browser for a short time over IE but allowed Chrome to take over and eat its lunch.

Now Firefox is declining into irrelevance. The EU Digital Markets Act demands for Apple to open up to more browsers with just cement Chrome's dominance and make Firefox even more irrelevant.

replies(1): >>acdha+jz2
◧◩◪◨⬒⬓
20. izacus+AC[view] [source] [discussion] 2023-01-24 15:24:07
>>snowwr+9w
No, allowing Apple to lockout all competitors to their browsers (and letting them keep gatekeeping even skins on top of their browsers) is command economy.

It outright prevents existence of new browsers and competition and it's a flagship examples of monopolistic corporations killing innovation and competition.

You yourself admitted that free market was required for current iPhone browser to exist and Apple locked out free market.

replies(3): >>snowwr+YF >>the_ot+kH >>girvo+ZM2
◧◩◪◨⬒⬓
21. izacus+WC[view] [source] [discussion] 2023-01-24 15:25:18
>>sbuk+1d
There is no "Gecko" on Apple platforms because you keep defending monopolistic lockout. It's utterly bizarre to defend megacorporation by scaremongering with a browser that isn't allowed to exist.
replies(4): >>artifi+2Y >>sbuk+R11 >>girvo+HM2 >>the_ot+nI3
◧◩◪◨⬒⬓
22. izacus+eD[view] [source] [discussion] 2023-01-24 15:26:55
>>snowwr+uw
Chrome will only be the better browser if Apple refuses to improve their own. This is how free market competition works - best browser wins.

You're now demanding to be forever locked into an inferior corporate owned product because you're utterly afraid that the better product would win. It's insane.

replies(2): >>snowwr+xF >>the_ot+II
◧◩
23. postal+SE[view] [source] [discussion] 2023-01-24 15:34:24
>>dicker+59
And for users who prefer keeping control. Why do you think reddit wants you to run their app and not their website on your device?
replies(3): >>pwinns+Um1 >>acdha+4B2 >>dmitri+Md4
◧◩
24. ch4s3+6F[view] [source] [discussion] 2023-01-24 15:35:22
>>dicker+59
I have never once intentionally or willingly used a PWA when an app was available.
◧◩◪◨⬒⬓⬔
25. snowwr+xF[view] [source] [discussion] 2023-01-24 15:37:38
>>izacus+eD
This is just really naive. When Google controls the back-end and front-end, they can introduce custom functionality that simply will not run in an alternate browser, no matter how good it is. Microsoft did this extensively in IE.
replies(1): >>izacus+Xl2
◧◩◪
26. the_ot+UF[view] [source] [discussion] 2023-01-24 15:38:56
>>samwil+13
Google already does this. G-suite is a Trojan horse for their browser, which is a Trojan horse for their advertising engine. They'll disable suite features, or make it mysteriously not run in your "outdated" browser. You'll have to move to something Google approved just to be able to collaborate with your team, or your friends.

> You can't fight or justify anti competitive behaviour with anti competitive behaviour back.

The way it seems to me, for this case, is that those two "anti-"s cancel out and leave you with direct competition?

replies(1): >>sebzim+1I
◧◩◪◨⬒⬓⬔
27. snowwr+YF[view] [source] [discussion] 2023-01-24 15:39:03
>>izacus+AC
You’re just mistaken about basic economic terminology.
◧◩◪
28. endemi+hG[view] [source] [discussion] 2023-01-24 15:40:21
>>moonch+kt
Here's just one example that I can remember of Google Search doing UA sniffing to serve a worse experience to Firefox: https://bugzilla.mozilla.org/show_bug.cgi?id=975444
◧◩◪◨⬒⬓⬔
29. the_ot+kH[view] [source] [discussion] 2023-01-24 15:43:59
>>izacus+AC
> It outright prevents existence of new browsers and competition and it's a flagship examples of monopolistic corporations killing innovation and competition.

No it doesn't. Tens of new browsers appear on multiple platforms every year, in parallel with Apple's approach. All of them fail to gain significant market share, and most of them are based on Blink.

The bigger obstacle for browser innovation is the complexity of making a modern browser. That complexity is actually partly driven by developers demanding constant feature expansion in browsers. It's been great having web apps explode, but also that makes browsers fiendishly complex.

◧◩◪◨
30. sebzim+1I[view] [source] [discussion] 2023-01-24 15:46:21
>>the_ot+UF
>They'll disable suite features, or make it mysteriously not run in your "outdated" browser.

Can you give an example of a G-suite (or any google product) feature that does not work in Firefox?

replies(3): >>Androi+8g1 >>error5+4E1 >>acdha+9z2
◧◩◪
31. acdha+AI[view] [source] [discussion] 2023-01-24 15:48:10
>>moonch+kt
All 3 of those sites heavily promoted Chrome to users of other browsers, inaccurately claiming that the service would be better with it (it wasn't).

YouTube also had an interesting example of the problem: they shipped some code using Chrome's early draft of what became Web Components. Firefox and Safari implemented the standard version, but there was a LONG period where YouTube used a very slow polyfill instead of upgrading to the standard version, causing Chrome to appear to be faster because it wasn't all of that extra JavaScript. If YouTube was an independent company they would likely have fixed a poor user experience much faster.

◧◩◪◨⬒⬓⬔
32. the_ot+II[view] [source] [discussion] 2023-01-24 15:48:29
>>izacus+eD
> You're now demanding to be forever locked into an inferior corporate owned product

Some of us are not. Some of us are saying "now is the wrong time to force Apple to open up its platform to other browsers". Safari on iOS is the one browser holding back Chrome from a monopoly for now. If you really want to see an open web, a more diverse web ecosystem, we have to expand the use of _other_ browsers such that there are again multiple, successful engines at the W3C; so that Google can't lock users out of their tools by forcing them to use Chrome. Only then will it be the right time to go after Apple's browser restrictions.

replies(1): >>jsnell+3n1
33. acdha+nL[view] [source] 2023-01-24 15:58:34
>>samwil+(OP)
Here's what Safari users don't get. Can you be precise about which ones are vital?

1. Install prompt (the user has to start with the "Add to Home Screen" command)

2. Link interception (i.e. browsing in the normal browser switching to the PWA rather than continuing normally)

3. Shared storage between the normal browser and the PWA

4. Ability to start fullscreen

5. SVG icons

6. Background sync

7. Push notifications

The rest of that is largely a list of things like "Web Bluetooth" which are non-standard Chrome features which Firefox also doesn't implement and often have significant privacy or security concerns.

replies(2): >>BeefyS+BS >>bouche+CS
◧◩
34. BeefyS+BS[view] [source] [discussion] 2023-01-24 16:21:57
>>acdha+nL
I would say every one of those except the SVG icons put PWA's at a huge disadvantage, to the point of being borderline unusable.

Do you feel like the current state of PWA's in iOS presents a viable alternative to publishing an app for any real usecase?

replies(1): >>kitsun+l71
◧◩
35. bouche+CS[view] [source] [discussion] 2023-01-24 16:22:05
>>acdha+nL
Push notifications alone are enough to force most apps to be native. But a lot of the other stuff missing is what keeps the experience from being quite as polished as a native app.
replies(2): >>acdha+BW >>dmitri+aX3
◧◩◪◨⬒⬓
36. saiya-+yT[view] [source] [discussion] 2023-01-24 16:25:39
>>snowwr+uw
Sorry to sound personal, but your arguments left the realm of facts somewhere up there. I see your account has some duration and karma, which negates the usual argument of paid marketing accounts, the practice so prevalent these days (and past decade).

As for walled monopoly - what if Apple allowed Firefox with its free extension model - what argument would you come up then? One can easily use ublock origin with Firefox, a thing Apple fears quite a bit - its by far the best ad-blocking and to certain extent tracking technology out there currently. We all know here on HN that Apple is moving to marketing more and more (currently 4 billion/year for them and growing fast), so they will never allow this unless forced by law.

Which is one of those situations where users lose and corporation wins (unless you consider ads and tracking a good thing when Apple does it, but that's... illogical to be polite).

replies(2): >>kitsun+r81 >>snowwr+9C1
◧◩◪
37. acdha+BW[view] [source] [discussion] 2023-01-24 16:34:54
>>bouche+CS
It might be interesting to go through the apps you have installed and see how many don’t work as web apps. For me it’s about 10%, basically Signal and apps which use Bluetooth to configure things and which I use almost never.
◧◩◪◨⬒⬓⬔
38. artifi+2Y[view] [source] [discussion] 2023-01-24 16:40:21
>>izacus+WC
If there is no "Gecko" on Apple platforms which engine does Firefox use on macOs?
◧◩◪◨⬒⬓⬔
39. sbuk+R11[view] [source] [discussion] 2023-01-24 16:53:48
>>izacus+WC
Funny, the gecko base web browser on my mac must be my imagination.
◧◩◪
40. kitsun+l71[view] [source] [discussion] 2023-01-24 17:13:12
>>BeefyS+BS
Having played with several PWAs on Android and Windows where support is better, I’m not sure that they’d be any more popular even if Safari filled those feature holes. The average PWA experience sits somewhere between underwhelming and uncompelling, primarily because SPAs in general are anything but consistently good. For PWAs to not be bad, SPAs need to stop being bad first.
replies(1): >>BeefyS+819
◧◩◪◨⬒⬓⬔
41. kitsun+r81[view] [source] [discussion] 2023-01-24 17:17:46
>>saiya-+yT
> what if Apple allowed Firefox with its free extension model - what argument would you come up then? One can easily use ublock origin with Firefox, a thing Apple fears quite a bit

It can’t be that afraid, because you can use the Firefox version of uBlock Origin in the WebKit-based iOS browser Orion[0] right now.

[0]: https://apps.apple.com/us/app/orion-browser-by-kagi/id148449...

◧◩◪◨⬒
42. Androi+8g1[view] [source] [discussion] 2023-01-24 17:47:18
>>sebzim+1I
While being 3 years old, this video [1] is a good example of some of the behavior Google uses when they find out you're not using Chrome.

[1]: https://www.youtube.com/watch?v=ELCq63652ig

◧◩◪◨⬒
43. pwinns+6m1[view] [source] [discussion] 2023-01-24 18:12:21
>>rs_rs_+xi
Because Google can leverage their position in other markets (search, video, advertising) to exert undue power in the browsing market. Their browser doesn't have to be better, they can just degrade site performance for non-Chrome browsers and claim Chrome is better--which they've done many times before.
◧◩◪
44. pwinns+Um1[view] [source] [discussion] 2023-01-24 18:15:47
>>postal+SE
So they can run ads where I can't easily block them, presumably.
◧◩◪◨⬒⬓⬔⧯
45. jsnell+3n1[view] [source] [discussion] 2023-01-24 18:16:27
>>the_ot+II
We've waited 15 years for Apple to compete fairly. Just when will the right time arrive? When Apple has finished choking the web platform to death?
replies(2): >>dmitri+uj3 >>the_ot+YI3
◧◩◪◨⬒⬓⬔
46. snowwr+9C1[view] [source] [discussion] 2023-01-24 19:10:28
>>saiya-+yT
Apple does not sell ads that load in a web browser, so I'm not sure why they would fear an ad-blocking browser extension.

Extensions, as originally implemented, are a security nightmare. That's why every browser, including Firefox, is changing the way extensions work. Firefox is keeping blocking WebRequest specifically for ad blocking, but acknowledges the security risk. Apple and Chrome are removing it, which breaks uBlock Origin.

Ironically you don't need to look any further than extensions to see the impact of giving the entire web to Chrome. Firefox said they have to implement Manifest v3 because "support for MV3, by virtue of the combined share of Chromium-based browsers, will be a de facto standard for browser extensions in the foreseeable future." Imagine what Firefox would need to do if Chrome was the only other browser, with near-total market share.

◧◩◪◨⬒
47. error5+4E1[view] [source] [discussion] 2023-01-24 19:16:45
>>sebzim+1I
TBH most everything works fine for me (unless I just don't know what I'm missing), but there is a very clear and frustrating gap with Meet backgrounds (blur etc.), which are artificially disabled on Firefox for dubious reasons.
◧◩◪◨
48. super_+cT1[view] [source] [discussion] 2023-01-24 20:14:13
>>snowwr+Qv
No Apple is not fighting back, it's forcing everyone to use safari/webkit based browser on iOS.
replies(1): >>acdha+Rz2
◧◩◪◨⬒⬓⬔⧯
49. izacus+Xl2[view] [source] [discussion] 2023-01-24 22:16:50
>>snowwr+xF
No, shilling for a megacorp monopoly to keep back the web because you hate another browser is naive.
replies(1): >>snowwr+OQ2
◧◩◪◨⬒
50. acdha+9z2[view] [source] [discussion] 2023-01-24 23:31:22
>>sebzim+1I
Meet used to say WebRTC wasn’t working and boot you out of meetings if you used Firefox. Every other service worked perfectly, but they clearly were slacking on fixing it for at least a year before we stopped using Meet.

GCP periodically breaks their console logins for Firefox users.

◧◩◪◨⬒⬓⬔
51. acdha+jz2[view] [source] [discussion] 2023-01-24 23:32:52
>>rvz+gB
“Allowed” is an interesting way to describe being the target of hundreds of millions of dollars in advertising and heavy promotion on several of the most popular websites in the world.
replies(1): >>rvz+MP3
◧◩◪◨⬒
52. acdha+Rz2[view] [source] [discussion] 2023-01-24 23:36:46
>>super_+cT1
Safari is quite competitive with Chrome - very noticeably faster at a fraction of the RAM and battery usage – and solidly dusted Chrome on the Interop 2022 competition all three vendors ran:

https://wpt.fyi/interop-2022?stable

◧◩◪
53. acdha+4B2[view] [source] [discussion] 2023-01-24 23:45:26
>>postal+SE
This is an interesting argument because while Google advertises the PWA concept as benefiting users, many of the features Apple and Mozilla haven’t shipped have been held back over privacy concerns. Reddit works fine in a browser, but the company wants to push you into the native app to get better ad data - they’re not going to support a PWA which gives you more control.

The biggest exception is Web Notifications and while that’s useful the desktop situation suggests there’s more than a little validity to the spam concerns. I would like that for a couple of sites but suspect I’d get really tired of selecting the “never allow” option in prompts.

◧◩◪◨⬒⬓⬔
54. girvo+HM2[view] [source] [discussion] 2023-01-25 01:11:36
>>izacus+WC
The Firefox I've been running on my Mac for 15 years at this point must be a figment of my imagination.

Of course I would love to see Gecko running on iOS. I just don't like the possibility of Google's browser dominance become even stronger either. It's a hard one.

◧◩◪◨⬒⬓⬔
55. girvo+ZM2[view] [source] [discussion] 2023-01-25 01:13:26
>>izacus+AC
> No, allowing Apple to lockout all competitors to their browsers (and letting them keep gatekeeping even skins on top of their browsers) is command economy.

That's a fundamental misunderstanding of the term.

◧◩◪◨⬒⬓
56. girvo+5N2[view] [source] [discussion] 2023-01-25 01:14:20
>>snowwr+uw
One can quibble about whether it is on purpose, but Google has done this with their web properties and Firefox, too.
◧◩◪◨⬒⬓⬔⧯▣
57. snowwr+OQ2[view] [source] [discussion] 2023-01-25 01:40:59
>>izacus+Xl2
I honestly do not understand the mental gymnastics that allow people to not count Google as (also) a megacorp.

The situation is not “Apple good, Google bad” or vice versa. The benefit of the current situation is that places these two huge companies in direct opposition and competition in the browser space. Using the law to force Apple to lose would take that away and cede the entire Web to Google’s control, thereby actually creating a monopoly.

◧◩◪◨⬒⬓⬔⧯▣
58. dmitri+uj3[view] [source] [discussion] 2023-01-25 06:22:04
>>jsnell+3n1
> When Apple has finished choking the web platform to death?

What a bullshit statement that has no basis in reality. I wish high-visibility "thought leaders" would stop spewing this bullshit (but they won't)

Safari is definitely not choking the web platform to death. It's as lively as ever.

What you want is a bunch of Chrome-only non-standards that both Safari and Mozilla vehemently oppose to, and a smattering of other bullshit features under the PWA banner that are coming to the next versions of Safari.

◧◩◪◨⬒⬓⬔
59. the_ot+nI3[view] [source] [discussion] 2023-01-25 10:15:30
>>izacus+WC
I use Firefox on macOS all day every day. It's definitely Gecko on an Apple platform. This monopoly you're talking about doesn't exist: it's two operating systems on two types of device.

I understand your frustration that you can't use the browser you want on the devices you want. That is annoying. However, *now* is the wrong time to go after Apple. Get more people using other browsers on other platforms first.

Wikipedia suggests this breakdown:

> As of November 2022, Android, an operating system using the Linux kernel, is the world's most-used operating system when judged by web use. It has 42% of the global market, followed by Windows with 30%, Apple iOS with 18%, macOS with 6%, then (desktop) Linux at 1.0% also using the Linux kernel.[1][2] These numbers do not include embedded devices or game consoles.

(from https://en.wikipedia.org/wiki/Usage_share_of_operating_syste... )

Android and Windows make up 4x the number of iOS users on the web. When the % of Chrome users on those platforms goes down, and Firefox and others go up, to a level where any of them could temporarily steer the direction the HTML/W3C standards take, _that's_ the time to go after Apple. Until then, lean on the fence Apple are holding up for you (and getting Google to pay for).

replies(1): >>sbuk+9D4
◧◩◪◨⬒⬓⬔⧯▣
60. the_ot+YI3[view] [source] [discussion] 2023-01-25 10:20:51
>>jsnell+3n1
> Just when will the right time arrive?

Android and Windows make up four times the number of web users as iOS. That's almost the same ratio (Chrome:others) as browser use across the web. Get a significant proportion of those user to move onto to other browser platforms first, then go after Apple give the final 20% of users more choice.

(based on stats from here: https://en.wikipedia.org/wiki/Usage_share_of_operating_syste... )

◧◩◪◨⬒⬓⬔⧯
61. rvz+MP3[view] [source] [discussion] 2023-01-25 11:27:38
>>acdha+jz2
Yes. 'Allowed'. After Mozilla claiming they can live without Google's money and knowing that they could not 14 years later. [0] Then getting itself sabotaged by Google for years [1] to be overtaken as the browser with the largest market share.

With Firefox's declining usage and market share, they are essentially on life support with Google's money since they know they would be completely irrelevant without it.

It appears that [0] has not aged well at all.

[0] https://web.archive.org/web/20120105090543/https://www.compu...

[1] https://www.zdnet.com/article/former-mozilla-exec-google-has...

◧◩◪
62. dmitri+aX3[view] [source] [discussion] 2023-01-25 12:35:09
>>bouche+CS
> the other stuff missing is what keeps the experience from being quite as polished as a native app.

Features HN developers think are missing from the web to deliver an experience "as polished as a native app": notifications, prompt banners, link interception, Chrome-only non-standards like bluetooth etc.

Features actual users think are missing from the web to deliver an experience "as polished as a native app": actual native-like experience: responsiveness, smooth animations, polished usable and accesible controls, maintaining scroll position and location in the app, fast scrolling through large lists, no loading states for the simplest actions...

I mean, people people keep bringing up Twitter's objectively bad web app as an example of one of the best PWA apps... Have these people never seen an actual native app?

◧◩◪
63. dmitri+Md4[view] [source] [discussion] 2023-01-25 14:22:30
>>postal+SE
> And for users who prefer keeping control.

The moment Firefox implemented one of the many hardware APIs aggressively pushed and promoted by Google, they immediately discovered it was used for fingerprinting: https://twitter.com/denschub/status/1582730985778556931

Chrome doesn't even show a prompt in this case. So much for "control".

replies(1): >>postal+V55
◧◩◪◨⬒⬓⬔⧯
64. sbuk+9D4[view] [source] [discussion] 2023-01-25 16:15:50
>>the_ot+nI3
Great post! The thing with people that "keep defending monopolistic lockout" as the GP put it, is they can see the bigger picture here.
◧◩◪◨
65. postal+V55[view] [source] [discussion] 2023-01-25 18:07:44
>>dmitri+Md4
Checked my settings and chrome defaults to prompt. Where did you read that chrome doesn't prompt?
replies(1): >>dmitri+mx5
◧◩◪◨⬒
66. dmitri+mx5[view] [source] [discussion] 2023-01-25 20:18:47
>>postal+V55
Could be they fixed it after this. Info on no prompt from the same person: https://twitter.com/denschub/status/1582730988118867968

--- start quote ---

Chrome still allows web developers to enumerate attached MIDI devices without user consent or even a notification, btw.

--- end quote ---

◧◩◪◨
67. BeefyS+819[view] [source] [discussion] 2023-01-26 19:04:07
>>kitsun+l71
A ton of "Native Apps" are SPA's using React native, Cordova, et al. The problem is not the tech, the problem is the arbitrary feature gating (including the kinds of tricks that React Native is able to leverage when packaging an app vs running in a mobile browser).
[go to top]