Product1 distinct publisher2 min readPublished
Apple, Samsung and Google fix support windows when a watch launches, not when it wears out. Eight working models stop getting fixes on a schedule that was set years ago.
The Product Desk · Product desk
Compiled by The Product DeskSomething wrong?How this is made
The expiry date is set before the box ships. Judson Dressler, who heads the risk operations center at the cyber risk company Resilience, told Fast Company that manufacturers pre-set a support window at launch and stop patching once it expires, mostly because maintaining older models costs engineering time and because new purchases are the point [2]. Nothing degrades. The watch keeps most of its functionality and simply stops receiving fixes for vulnerabilities discovered after the date [2].
Add up the affected models and the concentration is the interesting part: five Apple watches, two Samsung, one Google, which is where the total of eight comes from [13]. The earliest and latest of those cutoffs sit roughly four months apart [14]. For anyone managing a mixed-vendor inventory, that is one remediation window rather than attrition spread over years, and it arrives with dates attached instead of as an incident report.
The eight are not in the same condition, either. Samsung is the only one of the three that has split the two kinds of update: the Galaxy Watch 5 and Watch 5 Pro stop taking new Wear OS releases but keep receiving security patches, likely for at least another year [7]. That leaves six of the eight with no stated security tail at all [15]. A feature freeze is a nuisance. A device that no longer receives vulnerability fixes, while still paired to a phone, is inventory with a known defect.
Apple's case shows the limit of planning against a published policy. Its vintage designation applies five to seven years after it stops distributing a product for sale, which currently covers every Apple Watch through the Series 5 [3]. Yet the watchOS 27 compatibility list drops the Series 8 and the first Apple Watch Ultra while both sit inside the window Apple generally honours, which Fast Company reads as a chipset problem rather than a policy one [5].
Google supplies the cleanest number in the whole story, and it is a comparison against itself. Pixel phones get seven years of support [10]. The Pixel Watch 2 reached the market in October 2023 [8] and, according to Google's support page for the watch, has no guaranteed security updates or feature drops after October of this year [9]. The phone stays patched for most of a decade; the thing paired to it does not. When the two travel together into an office, the shorter window is the one that describes the pair.
Ranked by verification strength, evidence, and original report placement.
Apple, Samsung and Google are all ending or scaling back support for various smartwatch models in the coming months, affecting eight different smartwatches; some see updates cease within weeks, others continue through year's end.
"Smartwatches are deemed end-of-life on a fixed schedule, not because the hardware fails, but because manufacturers pre-set a support window at launch and stop patching once it expires," said Judson Dressler, head of the risk operations center at cyber risk company Resilience. "Most of the time it stems from engineering costs associated with maintaining older models and incentivizing new purchases. ... The watch should maintain most of its functionality after that date. What it stops doing is receiving fixes for newly discovered vulnerabilities."
Apple declares its products "vintage" after it stopped distributing them for sale more than five but less than seven years ago; as of publication that includes all Apple Watch releases through the Series 5.
Apple's list of compatible devices for watchOS 27 excludes the Apple Watch Series 6, Series 7, Series 8, Apple Watch SE 2nd gen and the first-generation Apple Watch Ultra; Apple will likely release watchOS 27 sometime in September but has not given a firm date.
The Samsung Galaxy Watch 5 and Watch 5 Pro both came out in 2022.
Wear OS updates issued after the end of this year will not be compatible with the Galaxy Watch 5 and Watch 5 Pro, but security updates will continue for the foreseeable future, likely at least another year.
Follow any of these and your For You feed starts watching them — no settings page required.
Evidence-backed comparisons of source perspectives and observed adoption signals. Read the methodology
Which Builder, Operator, and Investor concerns the observed source mix emphasized—not a truth score.
Evidence, demonstrated adoption, hype gap, incentives, and confidence are assessed independently, each on its own current evidence. How these are measured.
Vendor schedules documented secondhand by one outlet
The dated cutoffs rest on identifiable vendor artifacts - Apple's watchOS 27 compatibility list, Google's Pixel Watch 2 support page, Samsung's Wear OS compatibility statement - and one named expert. But everything reaches us through a single publisher with no vendor comment, no links or quotes from the underlying pages reproduced, and hedged wording ('likely', 'foreseeable future'). The causal and risk layers are weaker than the date layer: no confirmed reason for the Series 8/Ultra exclusion and no incident evidence behind the network-foothold scenario.
No exposure or usage data supplied
The cluster documents vendor lifecycle schedules but nothing about real-world exposure: no installed-base or active-user figures for any of the eight models, no upgrade or replacement rates, no enterprise fleet counts, and no observed exploitation. Vendor cutoff announcements are not adoption measurements, so the dimension cannot be scored without inferring numbers the source never states.
Obsolescence framing runs ahead of the stated facts
The framing ('could soon be obsolete', 'end of their lives') overstates what the article itself documents: the watches keep most functionality, Samsung explicitly continues security updates for at least another year, and the Apple cases are primarily an OS-version floor rather than a stated end of security patching. The lateral-movement threat is presented vividly with no incident evidence. The dates and the eight-model count, however, are concrete and correctly reported, so the overstatement is moderate rather than severe.
Upgrade incentives named; risk source is commercially interested
Two incentive structures are visible in the supplied material. Vendors: the article's own expert attributes fixed support windows partly to 'incentivizing new purchases', and the seven-year Pixel phone commitment against a roughly two-year watch guarantee makes the asymmetry concrete. Commentary: the sole security voice heads a risk operations center at a cyber risk company, so amplifying unpatched-device exposure aligns with his employer's business. No vendor was given a chance to respond, which leaves the incentive picture one-sided.
Dates credible, consequences unverified, one publisher
Confidence is limited by cluster structure more than by internal quality: a single publisher, a single expert, no vendor confirmation, and no way to cross-check the cited support pages. The model lists and cutoff months are specific and plausible, and the derived four-month window and security-tail asymmetry follow directly from the text. The causal claim about Series 8/Ultra and the network-compromise scenario remain unverified, and adoption is entirely unmeasured, so the overall picture is usable but provisional.
product
Samsung's Fold8 moves the foldable compromise, it does not remove it1 distinct publisher
product
White House lets vetted firms hack back and leaves liability blank for 60 days1 distinct publisher
product
Samsung's July foundry price rise moves the AI crunch into your bill of materials1 distinct publisher
product
Google tells Pixel suppliers to be out of China by 2027, and Vietnam is the template3 distinct publishers
Distinct publishers with included, body-backed reporting in this cluster.
1 article · August 24, 2026