Every few years, a pattern repeats itself with clockwork reliability. A major smartphone manufacturer announces a new flagship device. Within weeks, owners of two and three-year-old models start noticing their phones feel sluggish. Apps take longer to open. The battery drains faster. Scroll animations stutter. The timing is never a coincidence.
This is planned obsolescence in its most sophisticated modern form, and it operates through mechanisms far more subtle than anyone gives the industry credit for. Tech companies are engineering your software to expire on purpose, and the playbook is more coordinated, and more coldly rational, than most users suspect.
The Software Update as a Trojan Horse
The most effective mechanism for device slowdown is not hardware. It is software, delivered voluntarily by the user through a system update. When Apple released iOS 10.2.1, it introduced power management features that throttled CPU performance on older iPhones with degraded batteries. The stated goal was preventing unexpected shutdowns. The functional outcome was that devices felt noticeably slower. The company did not disclose this behavior publicly until a developer’s benchmark data surfaced and forced a response.
Apple eventually apologized and offered discounted battery replacements, but the episode revealed something important: the line between “protecting user experience” and “manufacturing upgrade pressure” is not just thin, it is frequently intentional. The 2017 throttling scandal resulted in class-action settlements exceeding $500 million across multiple jurisdictions, yet the underlying practice continued in modified forms.
Android manufacturers operate under similar dynamics. Qualcomm chipsets have documented thermal throttling behaviors that become more aggressive as processors age and accumulate heat stress. Samsung’s One UI has historically imposed background app restrictions on older devices that were not applied to flagship-tier hardware. These are engineering decisions with commercial consequences baked in from the design stage.
The Battery Is the Kill Switch
The battery is the most important variable in device longevity, and manufacturers know this better than anyone. Lithium-ion cells degrade with every charge cycle, losing capacity in ways that compound over time. A battery at 80% health does not just give you 20% less runtime. It also delivers current inconsistently, which creates voltage drops during peak CPU demand, which triggers protective throttling, which makes the device feel slower across every interaction.
This is real physics. But the business layer sits on top of it. Manufacturers set the degradation thresholds that trigger throttling. They decide whether to communicate those thresholds transparently. They choose whether to make battery replacement affordable and accessible. For most of the industry’s history, they made the opposite choice on all three counts. Batteries were glued inside devices. Replacement costs were priced near upgrade territory. Throttling happened silently.
The European Union’s Right to Repair regulations, which began taking hold in the early 2020s, forced some recalibration. Apple introduced self-service repair programs. Fairphone built an entire brand identity around modular, replaceable components. But these are exceptions operating within a system still optimized for obsolescence.
Feature Bloat as Planned Friction
Beyond battery management, there is a second, less discussed mechanism: deliberate feature inflation. Each new operating system release is engineered for current-generation hardware. The visual effects, the background processing, the new API requirements for updated apps, all of it assumes silicon that did not exist three years ago. Older devices receive the same update but run it on hardware that was not the target environment.
This is not always malicious. Software ecosystems must advance. But the decision about how aggressively to optimize for older hardware, whether to ship a “lite” update path, whether to cap certain devices at earlier OS versions rather than forcing degraded performance, these are choices with financial implications. A device that runs smoothly at age three is a device that does not generate upgrade revenue.
The pattern connects to a broader truth about how tech companies think about product timelines. Much like tech companies deliberately delay products that are ready to ship, they also manage the end of a product’s life with equal deliberateness. The upgrade cycle is not organic. It is engineered from both ends.
Why Regulators Are Finally Paying Attention
For most of consumer technology’s history, regulators treated device slowdown as a consumer protection nuisance rather than a systemic competition issue. That framing is changing. Italy’s antitrust authority fined Apple and Samsung a combined 20 million euros for practices that encouraged users to update software on devices unable to support it adequately. France introduced a repairability index requiring manufacturers to score and display how repairable their products are at point of sale.
The underlying regulatory logic is sound. When the dominant platform company also controls the operating system, the app ecosystem, and the hardware replacement cycle, the ability to influence device longevity through software is an extraordinary market power. The most valuable tech patents protect ideas that sound completely obvious, and the same principle applies to market control: the most valuable lever in the upgrade cycle is the one hiding inside a routine software update.
The repair and longevity movement is producing real competitive pressure. Samsung now commits to seven years of OS updates on flagship devices. Google followed with equivalent promises for Pixel hardware. These commitments emerged not from altruism but from regulatory pressure and the realization that longevity promises are themselves a marketable differentiator.
What Users Can Actually Do
The most effective countermeasure is also the least glamorous: replace the battery before it degrades past 80% capacity. Independent repair shops offer this service for a fraction of manufacturer pricing. Apple’s diagnostic settings now display battery health directly. Catching degradation early, before throttling activates, extends perceived performance significantly.
Delaying major OS updates on older devices is a second lever. The first three to six months after a major release are when optimization gaps are most severe. Waiting for point releases, the x.1 and x.2 versions that follow flagship launches, typically means running software that has been patched for a wider hardware range.
Finally, understanding that app bloat is a parallel problem matters. The apps you rely on most are themselves growing heavier with each release, independent of OS changes. An older device running a current Instagram or Google Maps is carrying software engineered for hardware it does not have. Lightweight alternatives exist for almost every major app category and the performance difference on older hardware is frequently dramatic.
The upgrade cycle is a system, not a natural law. It was designed, and understanding the design is the first step toward opting out of it on your own terms.
