371–380 of 515 posts
Earlier quoted context omitted.
The fact that some apps are broken and users with auto-update turned on are now unable to use those apps for a week?
Which apps are broken?
https://forums.macrumors.com/threads/ios-14-broken-buggy-app...
Earlier quoted context omitted.
I'm angry at Firefox because it was the only browser that I trust that allowed me to have extensions to solve my problems with bad websites on mobile and they removed them. But bad websites are not something we are going to get rid of using only iPhones...
The difference is that notification spam on the web is allowed to escape the sandbox. Because of the punch the monkey nature of the web, I inadvertently clicked “allow notifications” on both PCWorld and Tom’s Hardware on different occasions - they both spammed me at least once a day. But not enough to figure out how to disable it. To get rid of the cookie notifications, I can at least set web pages I go to default to…
The problem is that if Apple singlehandedly decide what's right and what isn't we are back to IE.
Maybe I am missing something, but iOS 14 has had beta versions out for developers for months; I had been running iOS14 and Big Sur for testing for weeks. Apple has always had developer previews and at some point, when mostly stable, they often release public previews to get a few interested users involved in testing as well. They've been working with developers for a long time on the new App Clips functionality and t…
Even major apps like Instagram and Snapchat still have critical camera bugs on my phone right now that's running the latest iOS14Beta8 build.
Earlier quoted context omitted.
Yes. I don’t want to press the “no” button for a 100 times.
You should lobby W3C to remove the API from the standard then. Or ask browser vendors to have a global allow/deny flag for every Web API
I don't want websites asking me to enable notifications. 99.9% of the time, the answer is no.
I don't want websites asking me to enable location access. 99.9% of the time, the answer is NO.
Nor do I want them asking for permissions to install to my Home Screen (the answer is no), or to track me (the answer is NO).
>Or ask browser vendors to have a global allow/deny flag for every Web API
When possible, I've carefully configured my browser to automatically reject these requests, but instead of respecting that, these websites, with all their hubris, have chosen to circumvent my preferences by presenting shitty JS-based permission requests (as opposed to using the permissions UI built into the browser).
Each one of these new web APIs have significantly degraded my experience as an end user, by presenting a million permission dialogs whenever I'm visiting webpages, without providing me with any features of value (again, because I'm not ever, ever gonna trust some random website with these permissions).
Users don't care to pontificate about the virtues of the open web, they just want their stuff to work. And until the open web can provide a better user experience, of course users are going to flock to various walled gardens (App Stores, Facebook, etc...). Until we find a way to implement web standards elegantly, without degrading the user experience, the open web is always going to face an uphill battle over the relative safety of walled gardens.
Earlier quoted context omitted.
This answer is wrong on so many levels... I don't know why Apple is allowed to keep other browser engines out of their system, but probably just because the relevant people just don't understand that the Chrome/FF/etc. on iOS are just a Safari with a different UI and that it gives Apple about half (depending on country; in the US probably more) of the mobile browser share and users just the chance to either use Andro…
Playing the devils advocate here. This browser restriction is what I'd wager is keeping the non-chromium browser market at a substantial proportion.
It’s a bit ironic, but browser engine monopoly on iOS is the only thing standing in the way of browser engine monopoly across all platforms.
Earlier quoted context omitted.
You should lobby W3C to remove the API from the standard then. Or ask browser vendors to have a global allow/deny flag for every Web API
I don't know if you're being sarcastic or not, but here's the thing: I don't want websites asking me to enable notifications. 99.9% of the time, the answer is no. I don't want websites asking me to enable location access. 99.9% of the time, the answer is NO. Nor do I want them asking for permissions to install to my Home Screen (the answer is no), or to track me (the answer is NO). >Or ask browser vendors to have a g…
I know I don't want them.
Apple is in the committee.
Earlier quoted context omitted.
Why wouldn't you use Android then? I would personally like to continue paying higher prices to protect myself from low-quality background-syncing byte-code-obfuscated web-pages with push notifications, please.
Safari on macOS supports push notifications and it hasn't intrinsically been a bad thing -- at worst, I have to tell a web site "no, I don't want your notifications." They're opt-in rather than opt-out like native app notifications are. The higher prices you and I are paying aren't protecting us from "low-quality" notifications as it is, anyway. At any rate, maybe you're so worried about single-page web apps being ba…
Native iOS notifications are opt-in
Earlier quoted context omitted.
Why wouldn't you use Android then? I would personally like to continue paying higher prices to protect myself from low-quality background-syncing byte-code-obfuscated web-pages with push notifications, please.
Safari on macOS supports push notifications and it hasn't intrinsically been a bad thing -- at worst, I have to tell a web site "no, I don't want your notifications." They're opt-in rather than opt-out like native app notifications are. The higher prices you and I are paying aren't protecting us from "low-quality" notifications as it is, anyway. At any rate, maybe you're so worried about single-page web apps being ba…
Disappointingly, Apple makes an exception for their first party apps.
Earlier quoted context omitted.
The first point doesn’t make sense to me at all. No particular date was set for when users would be able to install apps with the new features. Point two seems weak. The idea that Apple won’t promote apps with the new features when they are released makes no sense at all. You make it sound like this is unlikely, but I don’t see why you’d think that. As for excitement - what excitement are we talking about? Users will…
> No particular date was set for when users would be able to install apps with the new features. The expectation is that apps will support the new features on day one. Because that's how it has worked in the past. > what excitement are we talking about? Users will get app updates automatically as they become available. Again, historically, apps support the new features on day one. That won't be the case with this rel…
My guess is that Apple would have taken this into account when scheduling the release.
If there was some marquee feature where day 1 support was important, this would have been part of Apple’s planning.
It’s clear to me that this is really not a big deal at all and that the original author - not you - is trying to manufacture outrage where none is merited.
It’s also not clear to me that any significant end users would have reason to expect most apps to be updated on day 1.
Apps have simply never adopted all the new features they could, day 1 or not. Often adoption has been gradual. Even things that are very obvious like screen size changes sometimes have taken months to be supported.