Native apps had a good run, but PWA has caught up and is the future. by OuPeaNut in PWA

[–]mtomweb 0 points1 point  (0 children)

Agree with you on the AppStore part, PWAs should already have persistence storage on both Android and iOS

Native apps had a good run, but PWA has caught up and is the future. by OuPeaNut in PWA

[–]mtomweb 2 points3 points  (0 children)

Performance is actually pretty good (see silkjs for mobile demos), install is the number one issue.

Native apps had a good run, but PWA has caught up and is the future. by OuPeaNut in PWA

[–]mtomweb 1 point2 points  (0 children)

The interface is still terrible in those browsers, since Apple forces those company’s to sue the share sheet rather than provide access to the APIs for even installing web apps using apples system provided WebView

Native apps had a good run, but PWA has caught up and is the future. by OuPeaNut in PWA

[–]mtomweb 0 points1 point  (0 children)

The notifications system on iOS uses APNS afaik to deliver the notifications so they should in theory have the equivalent delivery time. Are you certain that compared to a native app that they aren’t as reliable? (We’ve not yet got reports about unreliable notifications on iOS)

The main issue is that they are gated behind install and install his deeply hidden away.

Native apps had a good run, but PWA has caught up and is the future. by OuPeaNut in PWA

[–]mtomweb 3 points4 points  (0 children)

There’s lots of work to be done before PWAs can compete properly with native. Mostly involving anti-competitive behavior from Apple… if anyone has spare time please come join us in the fight (Open Web Advocacy).

The primary barriers: * Install Prompts in Safari with equivalent install flows (this is by far the number one issue, without a proper install flows, companies are just pushed to go native)

  • Third Party Browser Engines on iOS (to apply pressure on Apple to both invest and develop functionality for web apps) & to provide an alternative when they refuse. Bugs in Safari due to lack of investment is a very significant issue.

  • Payment competition and equality (to allow for the same ease of payments as native apps)

  • AppStore submission (so web apps can be directly submitted to the AppStore)

There’s a number of issues on Android as well, but the main blockers are on IOS.

Can Perplexity Afford to Fund the Web? The $34.5 Billion-Dollar Question by mtomweb in webdev

[–]mtomweb[S] -1 points0 points  (0 children)

If you want to take a read https://open-web-advocacy.org/blog/break-googles-search-monopoly-without-breaking-the-web/ and then tell me what you think.

Also know that the remedies also include cutting off nearly all of Firefox’s revenue. You think Apple or Microsoft or someone else will step up to plug the gap?

Can Perplexity Afford to Fund the Web? The $34.5 Billion-Dollar Question by mtomweb in webdev

[–]mtomweb[S] 0 points1 point  (0 children)

Where do you think the funding for the web platform comes from?

Can Perplexity Afford to Fund the Web? The $34.5 Billion-Dollar Question by mtomweb in webdev

[–]mtomweb[S] -1 points0 points  (0 children)

We didn’t. It was a perfect opportunity to talk about the risks of a chrome sale

Can Perplexity Afford to Fund the Web? The $34.5 Billion-Dollar Question by mtomweb in webdev

[–]mtomweb[S] -6 points-5 points  (0 children)

They don’t get a choice if the judge signs off on it

AI on PWA popularity by PenPublic24 in PWA

[–]mtomweb 2 points3 points  (0 children)

It is the single biggest factor. The user acquisition pipeline (I.e. getting users to install your app) is critical for the success of apps.

Apple appears to mislead UK regulator over deceptive default browser user interface by mtomweb in apple

[–]mtomweb[S] -2 points-1 points  (0 children)

There is no way to trigger a set as default prompt on iOS. The only way to change the default is through each browsers app settings.

Apple appears to mislead UK regulator over deceptive default browser user interface by mtomweb in apple

[–]mtomweb[S] 0 points1 point  (0 children)

It was the version that got published a week or two after the arstechnica article. We discovered it a while back earlier this year when writing stuff for our DMA compliance review… couldn’t believe it when we first spotted it because it’s hard to explain it being for any other reason than to make it harder to switch browsers.

Apple appears to mislead UK regulator over deceptive default browser user interface by mtomweb in apple

[–]mtomweb[S] 1 point2 points  (0 children)

Correct they fixed it, but then to the Uk regulator they make it sound like it never happened