A web app still works from day one. Actually, many simple things are doable via web apps nowadays.Now I thought you could download an app from a website, using the browser, and add it to your phone. I know the corporation I work often distributes apps via a special web link. Does this not work at all? Since I haven't done this in a while, and also because it is a hassle to manually type the complete web address into the browser.
The issue is greedy huge companies like Epic
Sure. That's their business decision. Plenty of apps are not available on Android. Doesn't stop me from using Android as my daily driver. Alternatives will exist in the marketplace.Would you be okay with big name developers choosing to not make apps for iOS in the future? Would you think "you know, that's fair! Choice!"
I never said Apple themselves was not greedy.You misspelled "Apple"
I find the pro-apple arguments on this so mystifying.
Do all of you want the Mac locked down as hard as iOS also?
They all think this way because their app ecosystem already exists, and can afford to be complacent. Now if and when a developer exodus starts picking up movement due to these unattractive terms, and big names apps begin to go away or go web-only, these same people will be like "now wait a minute, that's not what I meant..."
I give you credit for actually tackling notarization, which even Apple doesn't want to discuss with respect to iOS. I don't agree with your conclusion, but appreciate the posts. I think notorization is a reasonable solution and trade off, and frankly, one they've already made with enterprise certificates on iOS.If this is just as secure then why don’t they just put their App onto the App Store? Why have side loading with notarization at all? If their App is good then just put it on the App Store no need to have a side loading option.
The purpose of notarizing is to scan the software for malicious content and use of unsigned code along with other things, stuff that already happens with the App Store. However if a developer‘s ID signing key is exposed to a bad actor they will then be able to distribute Apps onto your iOS devices that can compromise you data. So in this case you make a honest app that is harmless and does what its suppose to do. Someone gets your developer key and your app and inserts malicious content into it and uses your key. Now its notarized and gets on others iOS devices and does its work. Apple will likely eventually catch it but not until after it has done its damage and likely gotten loaded on many other iOS devices. You can read up on it here. However I’ve quoted Apple’s paragraph below. So yeah Apple’s notarized apps aren’t as safe. I don’t know if Apple claimed them to be safe, just better than not having anything at all.
Quoted from Apple:
Notarizing macOS Software Before Distribution
“Notarization also protects your users if your Developer ID signing key is exposed. The notary service maintains an audit trail of the software distributed using your signing key. If you discover unauthorized versions of your software, you can work with Apple to revoke the tickets associated with those versions.”
So this means the developer has to be on top of this and Apple may not catch it first if a developer‘s key has been compromised. This is especially bad for people who don’t have large operations like Microsoft or even folks who made an App that wasn’t all that popular and basically have abandoned it but get their key used for other bad stuff.
Gatekeeper was a ban-aide that Apple came up to try and allow customers a safe way to load apps onto their Mac that would safeguard them. However its just a not completely affective which is a good motivator for Apple to not implement it on their iOS platform.
Oh come on. Do you read every EULA and ToS out there? Ever since Windows 3.1, consumers have been trained to just click "Next" or "OK" to get through dialog boxes without reading. I just have a friend that literally allow a virus into her PC despite the browser and Windows showing up the warning dialog box. Not because she wanted the virus, but because she just automatically click allow/OK by habit.I don't know how much more explicit those prompts have to be. But if you're John Q. Public & after these prompts still proceed to open this... that's on you. You qualify as a dumbass. Why should some dumbass prohibit me from sideloading apps on my iPhone or iPad? They don't on the Mac. The point is the guardrails are there on macOS & would work on iOS/iPad OS.
I agree that there would be more competition in terms of app stores, and there would be a negative to Apple's bottom line, here. The issue for some of us isn't competition, it's the security of our devices being compromised for the sake of more competition.Forcing a locked down platform more open makes it more exposed to competitive forces on key aspects and lowers barriers to switching. It increases competition and makes choice more of a practical reality for users on both sides.
You don't understand choice, do you.Forcing a locked down platform more open makes it more exposed to competitive forces on key aspects and lowers barriers to switching. It increases competition and makes choice more of a practical reality for users on both sides.
And you're also correct. Most people don't think about it, and guess what, they're fine with it.You're assuming the "walled garden" is the product. I don't believe most people who buy iPhones think about or care about this at all, just Apple fans.
LOL what? Look at Android. Fragmentation at its finest, but that's the beauty of it. Why do you want to regulate that? Do you want government to regulate how OEMs make Android phones?Also, let me play devil's advocate and take "choice" to its conclusion: there are now 20 phone platforms to choose from. Sucks, doesn't it? That's why we have limited choice, that's why we have a duopoly, because fragmentation is inconvenient. So that's why we need regulation on these general-use, life-important platforms, because people don't naturally want 20 of them in the name of competition. Kinda like utilities going to your home.
I can purchase Spotify directly outside Apple’s App Store. I paid for YouTube premium without going through Apple, and still enjoy YouTube Music on my iPhone. I can purchase Kindle books just fine on Amazon.com, and I can access that through Safari.Regulate is a "hands off" meaning, not a "hands on" like is often painted. Regulation wants you to relinquish your iron-fisted grip and facilitate competition in the app ecosystem. Allow people to purchase Kindle books from the app the same way they can with Apple Books. Allow people to sign up for Spotify for $9.99 just like you can sign up for Apple Music for $9.99 in-app. You're taking the argument to Android (I also stated the duopoly was a natural conclusion of competition, btw) while ignoring there is an entire competitive economy inside of the iPhone people are already entrenched into, just like the utility you have to use to your home and can't easily switch out willy-nilly.
Its not really about agreeing with my conclusion or my view. What I think is that Apple doesn’t want the malicious content getting onto their iPhones because they would need to be responsible for it. Enterprise certificates work completely differently. These Apps are distributed by a company and can only be used by people inside that company. So they aren’t technically for the public. That business is also responsible for its distribution and still has a lot of restrictions on how it can function on the phone and usually can only access company internal materials. You can read about it here. Specifically the paragraph I quoted.I give you credit for actually tackling notarization, which even Apple doesn't want to discuss with respect to iOS. I don't agree with your conclusion, but appreciate the posts. I think notorization is a reasonable solution and trade off, and frankly, one they've already made with enterprise certificates on iOS.
If developers can’t run a business on their 70% from the App Store, then they need to hire a business manager. There are PLENTY of wise business folks that are able to derive profits from far slimmer margins than that. If your app sells $500,000 and you can’t run a business on $350,000, that’s a developer problem, not an Apple problem. Giving a developer that can’t run a business the full $500,000 means they’d blow through that irresponsibly as well and be looking at Apple to subsidize them… rather than make an app that sells well and run their business responsibly.I like the protection of the App Store, but I don't appreciate the financial abuse developers have to suffer when delivering apps through it.
Well, wouldn’t you think that designing, prototyping, producing an OS and shipping 100+ million iPhones and even more iPads a year is “working”? I mean, it must be harder than anything the developers are doing because I don’t see any developer being successful at it. Or, even trying for that matter.Apple is terrified of having to work for all that money they charge developers.
And, the thing is, it’s even incredibly small on Android as well. There’s a very, very tiny percentage of folks on Android that ever sideload. To the overwhelming majority of folks using smartphones, sideloading just isn’t a thing.I think it's best to keep side loading disabled. The benefit of having an incredibly small Percentage of users being able to side load a small number of app is far outweighed by the safety that comes to hundreds of millions of users be keeping it disabled.