> They introduced some BLE features before the spec was finished
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.
The only reason Apple ditched Lightning port and finally gave USB-C port in the iDevices, is because EU forced Apple to do so. But do you think your oh-so-common USB-C cables will work with a new iPhone?
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.
Couldn't you just upgrade yourself in the pre Apple silicone days?
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
"Seem". Until they don't. I've had multiple instances of Airpods stopping to connect with phones until I charged them at least once with original Apple cables. They might work fine for months, then stop ehaving unless connected through an all-Apple power pipeline (cable and charger). It's probably firmware updates requiring some sort of validation every now and then.
Sounds like you have a flaky / damaged device or bad cables. If there really was some kind of conspiratorial timer requiring you to use 1P cables it would certainly be documented. Can’t hide that stuff. Loads of people use Apple devices with 3P cables all the time and they work just fine, as long as the cables aren’t junk. There really are quality and capability differences in USB C cables. Just because it looks right and physically connects doesn’t mean it can electrically do all the things.
I know that Apple MFI certified Lightning cables work well with iDevices, but I found that third-party non-MFI-certified Lightning cables to be finicky with iDevices. But I never faced such problem with USB cables for non-Apple devices (Android phones, cameras, etc.).
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.
>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 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.
In my experience, the only 2 mobile phone companies whose phones drain battery too fast are Apple and Samsung. Apple does this deliberately for older phones, whereas Samsung has this problem even for new phones.
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.
I don't think you can find any evidence of a
Apple actually deliberately doing things to make batteries drain faster on older models.
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.
That iFixit guide to upgrade the Max Mini is daunting for newbies.
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.
You’re just limiting yourself for no reason. It’s not Apples fault that you are sitting in front of an un-upgraded computer that is tool-less (for one of your tasks, at least) and has step by step instructions meant for beginners.
That's because SMS is a horribly broken, hacky standard, and RCS has to inherit and deal with all the horrifying edge-cases of SMS, MMS, and legacy cruft going back prior to the turn of the millenium.
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.
The specific issue I'm talking about is how Apple for some reason ties the presence of RCS persistently to a contact that requires the user to manually go in and adjust, otherwise the conversation switches back and forth between SMS and RCS as each participant texts back and forth.
This is a problem no other vendors have, and is solely caused by Apple.
Why is that on Apple instead of the hundreds of other manufacturers and Google? If Google wants a better ecosystem, it’s on them since according to them Android was suppose to be the “definition of open”.
Because while Android is "open", Google has no carrot (Verizon can't charge for OTT messaging and has no major incentive to push it), and no stick (pushing too hard will draw regulators' attention again)
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)
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.