Your second quote conveniently chops out the main point of the article, which is that Apple abuse their dominance to force developers into having no choice.
What are the options in the smartphone landscape? Please elaborate in a way that my elderly mother could use without 24h tech support from family members.
Android? And have instead of golden handcuffs a straight-out chain to serve the ads landlord? Yeah there's only a "choice" between the comfortable golden cuff of Apple and the being actively exploited by google. I know what to choose.
Obs. For anyone suggesting giving a de-googled lineage phone to my mother, just, please, don't.
ftfy. I get a bit fed up with seeing these things promoted. I’m from New Zealand, not the US or Europe. Where do I get one? Who fixes it when it buggers up? Why does it cost so dang much? Why is it such a slow piece of crap compared to my iPhone 11? etc.
To me Apple stopped being on fire for a while now, in particular as we switched from broken keyboard laptops to wonderful ARM laptops only available in small sizes with 2 usb ports. Also on principle Apple barring third party browser engines and game streaming are two huge no-go, in continuation to the selective ban on interpreted code which almost kills the editor ecosystem. Those handcuffs are not that golden, really.
How so?
I think I could easily pull all my data out. Files are, well, files; contacts and calendars can be exported in standard formats; photos are stored as JPEG or raw; music is MPEG-4; e-books are epubs; whatever.
Sure, I'll lose some features, but that's because other platforms don't offer those features, not because Apple is heinously putting extra effort into locking up my data.
Are you sure ? I don’t use iBook but it doesn’t look to me like you can just export them as e-pubs and be done with it: https://www.igeeksblog.com/how-to-export-ibooks-from-iphone-...
- Try to export your photos from Google Photos
- Try to export you photos from Apple Photos
Let us compare those two, shall we?
Google Photos:
- stored in cloud
- no _synchronisation option_
- export exists but you loose metadata unless if you do it through API so third-party sync is not possible as well
Options to get your data back:
- Manually select all the photos in web ui and click download.
- Use google takeout option.
Apple Photos:
- Synchronisation. Go to settings and click checkbox "download everything to this Mac". Same for iPhone. Offline ready, your data is on your device.
- Export - just go menu and click "Export originals". It will conveniently organise your photos into files and folders. No internet connection required because the data _is already on your computer under your control_.
So, to answer your question. If Apple stops being on fire, I export my data in a single click and move it somewhere else if there's any option. But it will be sad day because I'm afraid that there will be no option, besides Apple the market is filled with liquid shit that treats users as cattle.
P.S. The example of photos works for everything else - my music library is synchronised and downloaded locally on multiple machines. If you've got Apple Music subscription you can drop anything in there and it'll upload it. Basically dropbox with UI of iTunes and Spotify on a side.
Same for iCloud Drive - it is downloaded locally. Heck, everything is downloaded locally, stored on my Macs and backed up with time machine. My data is under _my_ control when I go with Apple.
The problem is not the social sign in aspect, but that fact Apple forces you to implement it if you use their competitors' service.
Had Sign in with Apple not been mandatory, but merely something customers would ask developers for, then I'd consider the framework to be fair game. This simply isn't that.
If they didn’t force developers to adopt this, they would never do it as it’s in their interest to harvest the e-mail addresses of their customers.
So anybody who is using Sign In with Apple trusts Apple to do the right thing.
Besides, what monopoly? Apple is perfectly happy with other single sign ons — provided you also offer Sign In With Apple.
It is pretty standard "embrace, extend, and extinguish" strategy. Similar to what's happening in the browser market. They are waiting for majority of the apps to have their sign on and majority of users use Apple sign on, then update the policy to disallow other methods.
I mean I don't have any issue of Apple doing these in their own ecosystem, but at least don't be so hypocritical or naive when defending them.
If the only other options you provide are Google or Facebook, you (as an app developer) clearly doesn’t care that much about privacy.
Apparently Apple doesn’t feel that any other providers care enough. That’s why they’re mandating the use of their privacy-focused solution.
They are using their app store monopoly to gain a foothold in the single sign-on business. You could try to claim that there's no business there but look at how Microsoft got spanked for giving away a free browser. Now the Apple has over half the phones in the United States, I'm looking forward to them getting spanked very soon hopefully.
Yeah, it's practically the same thing if you just ignore the basic facts of the case.
That's exactly the kind of behavior that Apple is exhibiting here.
It's pretty easy to come along and say that I'm "ignoring the basic facts of the case" though without presenting any facts of your own to back that up. So let's hear your take now.
[0] https://en.wikipedia.org/wiki/United_States_v._Microsoft_Cor....
But again, Sign In with Apple sits in addition to the other offerings, it doesn’t replace them, and in no case are developers expected to be unable to offer regular sign in with email.
To my mind, you’re not wrong, but making a rather different argument.
They don't, and aren't trying to. They are trying to disrupt the Google/Facebook duopoly in the SSO space. Devs are free to require new accounts that they have the email for, just not outsource it to FB/Google.
the rule seems somewhat orthogonal to developers getting emails. Developers can still request login by the old school email-and-password with (or without) sign-up verification by email. On the other hand, some third-party logins don't give developers their users' contact information (just a token to verify that they're on their platform with no authentication permissions, or a dev can request that this be so else the third-party will inform the user that the dev is requesting their contact info).