Yes I want more shitty web apps. Also you can’t imagine how much I love cross platform Electron apps. I have no desire for random websites to have that much access to my phone.
Apple's intentional crippling of Mobile Safari
211–220 of 343 posts
Re: Apple's intentional crippling of Mobile Safari
#212Absolutely nothing listed on that site as unsupported by Safari has any business being part of the web. In fact several supported APIs should be chucked too. Fuck giving websites motion data or push notifications.
Re: Apple's intentional crippling of Mobile Safari
#213Yes I want more shitty web apps. Also you can’t imagine how much I love cross platform Electron apps. I have no desire for random websites to have that much access to my phone.
People like you could turn off these features and continue installing and updating native binaries for the Starbucks app or random hardware companion apps all you want. I'd like first-class PWAs please.
https://slack.engineering/reducing-slacks-memory-footprint/
When the obvious answer I gave about how to reduce the memory footprint and make it more performant was “to stop using fucking [web technologies]” and create a native app
But the question I always ask people who say that it’s mean old Apple keeping PWAs back, why is it that all of these same companies see a need to create an app for Android?
Re: Apple's intentional crippling of Mobile Safari
#214Earlier quoted context omitted.
From the perspective of avoiding a web that's wholly controlled by Google? Yeah, absolutely.
Letting my users have access to the Web Bluetooth API is not making Google somehow take control of the web. If Apple won't implement it, and they won't allow other browsers on their platform, that's plainly an abusive business tactic. It's far worse than what Microsoft did by simply include IE with Windows - Microsoft never forced every browser application to use Internet Explorer. Can you imagine the outrage if they…
Re: Apple's intentional crippling of Mobile Safari
#215I am curious why Safari in particular is getting a lot of the hate here when firefox supports even less of the features which leads me to believe that the reason many of these features have not been accepted is because they have not been accepted by the larger ecosystem and is just google pushing their own things as standard (Feels like IE days in many ways). That being said, I am not sure why I would actually want m…
Firefox is not in a position where it is the only browser allowed to run on a platform. On iOS, you’re either doing a native app, sharing 30% of your income with Apple, or you’re restricted to Safari’s feature set. No browser in iOS can use anything but WebKit
The other companies that are making money from mobile are usually front end for services that don’t monetize directly through in app purchases or give you the option of not paying through the App Store.
The first million in revenue is 15% not 30%
But also if it is just Apple, why do the same companies create apps for Android?
Let’s say in this world where there was an alternative browser engine that supported everything that you wanted, how much uptake do you think you would have for your app if someone had to download an alternate browser first?
Did I also mention that in the US at least you can link out to your own payment system?
Re: Apple's intentional crippling of Mobile Safari
#216Earlier quoted context omitted.
Even so, conflating "Safari is holding the web platform back by not implementing standardized web features" with "Safari is holding the Google platform back by not implementing non-standard Google features" is kind of disingenuous. Going through some of the list from the top: * Shortcuts in the manifest: This seems to be standard. Would be nice if mobile Safari supported it. * Protocol Handling: This is non-standard.…
>Even so, conflating "Safari is holding the web platform back by not implementing standardized web features" with "Safari is holding the Google platform back by not implementing non-standard Google features" is kind of disingenuous. You missed the point completely. Apple >forbids any browser engine on iOS other than their own Safari. So you can't just install Chrome on iOS, because when you do you get Safari instead.…
Do you really think that you are going to get any level of monetization by forcing users to first download a hypothetical web browser that has all of the features you want? That web browser doesn’t exist on any mobile platform
Re: Apple's intentional crippling of Mobile Safari
#217Earlier quoted context omitted.
Mobile safari is arguably the only thing standing between Google and total browser dominance. It's the reason why Google "only" has roughly 75% of the mobile browser market even though it has a 90% market share in desktop. I'm principally against the idea that Apple can prevent users from installing the software they want on their own devices, but we can't deny that it's better for the health of the web. Anyway, if y…
You clearly haven’t tried to design anything complicated that has to run on safari iOS. Safari iOS is a massive piece of shit. I’ve been working on a web game for a while now using canvas and most of my pain comes from making it compatible with safari. So much stuff is broken on safari so you have to find work arounds. Like a simple but annoying one, CSS filters don’t work on canvas so you have to write all those fil…
Re: Apple's intentional crippling of Mobile Safari
#218Earlier quoted context omitted.
You seem to be conflating my opinion of "iOS's lack of browser choice has the consequence of preventing Chromium from achieving total dominance" with some imaginary other person's opinion of "iOS's lack of browser choice is a benevolent act where good guy Apple valiantly defends the open web". I do, frankly, think that mobile Safari couldn't compete that well in an open market, just like desktop Firefox can't. (Not p…
Let Google dominate the web. If that’s a problem we can sort that out. But two wrongs don’t make a right.
No thanks
Re: Apple's intentional crippling of Mobile Safari
#219Earlier quoted context omitted.
You seem to be conflating my opinion of "iOS's lack of browser choice has the consequence of preventing Chromium from achieving total dominance" with some imaginary other person's opinion of "iOS's lack of browser choice is a benevolent act where good guy Apple valiantly defends the open web". I do, frankly, think that mobile Safari couldn't compete that well in an open market, just like desktop Firefox can't. (Not p…
Let Google dominate the web. If that’s a problem we can sort that out. But two wrongs don’t make a right.
Re: Apple's intentional crippling of Mobile Safari
#220Earlier quoted context omitted.
Letting my users have access to the Web Bluetooth API is not making Google somehow take control of the web. If Apple won't implement it, and they won't allow other browsers on their platform, that's plainly an abusive business tactic. It's far worse than what Microsoft did by simply include IE with Windows - Microsoft never forced every browser application to use Internet Explorer. Can you imagine the outrage if they…
You're shadow boxing. I never said Apple isn't engaging in abusive business tactics. They clearly are. I just think the result benefits the open web by taking power away from Google.
Which I think is far worse than anything you think Google is trying to do.
I'm not giving Google a free pass here, sure they can be abusive, I hated "AMP" and I'm glad it got thrown on the junk pile. That was clearly abusive. But implementing Web Bluetooth? Not abusive, it's progress. And it's too bad Apple abuses their power and stifles progress in this case.