I haven’t used non apple earphones for awhile but the seamless connectivity performance of AirPods would suggest this was done for performance, not to deliberately lock in devices.
This 2020 paper is great at breaking down some of the extensions: https://www.usenix.org/system/files/woot20-paper-heinze.pdf
In their defence, they went with Lightning shortly before the USB-C spec was finalized. Then, to avoid their customers being screwed over by constantly changing the connector, they kind of had to stick with it for a decade.
People will complain if they push features that are ahead of the spec, and they'll complain if they let the spec be finalized before they use it. Being guided by "What's the best we can do for UX, assuming out users are our users in every product category we enter" seems to be their reasonable middle ground.
Because they needed a way to get audio to the AirPods wirelessly and to work with their devices? That’s a pretty good reason to use Bluetooth.
I doubt they got together and tried to scheme a way to break Bluetooth in this one tiny little way for vendor lock in. You can use the basic AirPod features with other Bluetooth devices. It’s just these extended features that were never developed for other platforms.
HN comments lean heavily conspiratorial but I think the obvious explanation is that the devs built and tested it against iPhone and Mac targets and optimized for that. This minor discrepancy wasn’t worked around because it isn’t triggered on Apple platforms and it’s not a target for them.
In my country (India), Apple still doesn't sell charger and cable along with its new iDevices, even though those gadgets are exorbitantly expensive. And Apple doesn't allow custom repair here, even though my country mandated the Right to Repair, like EU did so. My old Mac Mini 2012 is gathering dust in a cupboard, because Apple service center refused to upgrade it to new RAM and new SATA SSD, citing Apple policies.
I do rather hope perhaps perhaps perhaps the EU & DMA or other may perhaps bend Apple off their rotten course of making non-standard bespoke systems. It seems like very recently the EU is getting ready to cave & abandon all their demands for trying to use standards, that their fear of the US is about to make them fold on insisting upon better. Demanding Apple stop doing everything in bespoke incompatible ways is something that should have happened a long time ago, imo, and it's so horrifying to see one of the only stands in my lifetime against the propeietarization & domination of systems by a bespoke corporate lord abandoned.
There's some rays of hope here & there. Seemoo Lab has a ton of amazing reverse engineering efforts, figuring out how many many many undocumented locked down Apple systems & protocols work & trying to give control back. This is the highest virtue, the best hacker nature. Here's Open Wireless Link, but they have so many other amazing projects they've similarly figured out out to pry open. Amazing best human spirit. https://github.com/seemoo-lab/owl
Like within minutes, with no big changes?
I didn't think it's rare that a company refuses to do any work on devices they no longer support. Their employees will no longer be trained to do this work, hence they'd have a nontrivial chance of causing damages. That's exactly why a right to repair is so important, so that other people can pick up their slack
The SSD is a bit more fiddly, but can also be done at home. Check iFixit.
https://www.ifixit.com/Guide/Mac+mini+Late+2012+Hard+Drive+R...
Some pictures here: https://www.reddit.com/r/assholedesign/comments/b1u08k/this_...
They seem to work just fine, yeah.
Support is very expensive. Say what you want about Apple, but they provide absolutely stellar support, especially with the stupidly inexpensive Apple Care insurance. This is only cost effective if they can make reasonable predictions about how their devices will behave in any given scenario. Interfacing Apple hardware with non-certified (MFi, BLE, etc) third party hardware has a non-trivial risk of unpredictability high support costs, either from excessive Apple Care claims, customer support communications, or just overloading the Genius Bar.
Reducing support cost could easily explain the motivation of the entire walled garden if they are sufficiently high.
But you've inspired me to gather courage and do the DIY upgrade myself next month during the holidays. No use having a working PC lying unused, merely because it is very sluggish due to old hardware. Wish me luck (for the upgrade), I think I'll need it.
No conspiracy needed, surely it would be unilateral? It seems exactly the sort of thing Apple Computers would do to protect their ecosystem.
Truth is, no one has the full facts so any reasons as to why this was made the way it was is pure speculation. Only a fool would move to condemn or endorse what is not yet fully understood.
Less friction for devices like passkeys, external hard drives, etc.
It doesn't seem like they were keen on moving that down the product line since they had to be dragged kicking and screaming to do so.
And what do you mean by "conspiracy"? I would be shocked to find out this was done by some lone wolf and wasn't built with broad (even if grumbly) consensus in the relevant teams. That's how corporate software is built.
That's not Apple's fault per se, but of course, they contribute to it. They should open up the iMessage protocol.
Then it has to accomodate every other intersted party, many of which hate each other. Apple has always been a bit of an odd duck ("Think Different" has been internalized for some time), but Verizon actively hates OTT messaging as they can't charge for it. Samsung would rather run their own RCS implementation to create and advertise "Samsung RCS", and Google can't push too hard without getting EU attention for antitrust (again).
RCS has been stuck in limbo-hell for years for multiple reasons, none of which are easy.
RCS has been stuck in limbo-hell for several years, and I expect it to stay that way (to your point, I expect it to stay that way even if Apple chips in)
But you can have an extension cord which accepts USB on one end but doesn't accept USB on the other.
So the keyboard has a superset connector so that it can go in regular USB and notched USB, because it is verified to work right when using the extension cord.
This design also means you can't plug one extension cord into another to get an even longer distance (which the keyboard wouldn't expect). Pretty clever solution.
This is a problem no other vendors have, and is solely caused by Apple.
https://www.androidauthority.com/android-iphone-rcs-messagin...
Apple MFI certifies USB-C cables also, so I'm not sure if it is throttling its iDevices to be finicky with non-MFI USB-C cables.
I know for a fact that Apple did software updates to older iPhones to make them sluggish and drain battery quickly. I realised this when I went to Apple Genius Bar to get my iPhone 7 Plus battery replaced after it started draining too quickly daily, but even with new battery same problem persisted. The friendly staff member unofficially told me it is because of the recent software updates by Apple for older iPhones, and advised not to hold out hope that any future software update will fix the problem. Even a year later, his warning remained true. I gave away the iPhone to my nephew as a backup device for his studies, but he sold it soon, as it was a nightmare to keep charging it frequently.
Apple has faced multiple fines for deliberately slowing down older iPhones without informing users, including a €25 million fine in France and a $41 million fine for deceptive marketing practices. The company admitted to slowing down devices to prevent unexpected shutdowns due to aging batteries, but critics argued it was misleading.
These days, I wouldn't trust Apple with a barge pole, let alone the money from my wallet.
These cases are much less convincing than they may seem if you just take a moment to read about them. iDevices would throttle the cpu to make the battery last longer as it's capacity falls, this kind of throttling is not uncommon and not malicious.
This wasn't misleading, and isn't something that warrants any genuine criticism.
You will not find this quick battery drain problem in Motorola, Nokia, Oppo, Sony, etc. Their phones last several years even with ageing batteries. An 10+ years old Oppo phone I have, still holds almost full charge at idle, throughout the day.
As batteries get older, their capacity to hold charge reduces, but if a phone battery is draining too fast even in idle mode, it is likely due to software, not hardware. And if it is due to software, then the manufacturer company is to blame.
That would either require hurting the battery life on all models or require distinguishable behaviours that only occur on specific models and would be relatively simple to prove through reverse engineering.
Apple has been fined for the throttling, but hasn't ever been credibly accused of actually deliberately taking steps to reduce battery life on older devices.