The $799 Apple Watch and the Support Deadline a Lawsuit Says Was Never Disclosed

The Facts

On August 12, 2026, California resident Richard Goetz filed a proposed class action in the federal trial court for the Northern District of California. He alleges that Apple sold premium smartwatches without disclosing how long they would receive major operating-system updates, then excluded five Watch lines from watchOS 27 while their hardware remained usable.

Goetz’s own purchase anchors the case. According to the complaint, he bought an original Apple Watch Ultra with cellular connectivity from Apple’s Stonestown store in San Francisco on December 17, 2022. He paid approximately $799 and purchased AppleCare+ at the same time.

The filing says he expected a device at that price to remain eligible for major watchOS releases for substantially longer than approximately four years. It does not allege that his Watch had physically failed when the case was filed. Instead, his claimed injury is economic: reduced value, a shorter expected useful life and the loss of future major software functionality.

The proposed class covers California residents who purchased an Apple Watch Series 6, Series 7, Series 8, second-generation SE or original Ultra. “Proposed” matters: a judge must still decide whether the case satisfies the requirements to proceed on behalf of a group. Until that class-certification decision is made, Goetz is the only named plaintiff in the supplied filing.

How Five Watch Lines Reached the Alleged Cutoff

The complaint describes the Apple Watch as a wearable computer rather than an ordinary watch. Its health monitoring, communication, navigation, payment and safety functions depend in varying ways on watchOS, iPhone compatibility and third-party applications. The filing argues that the duration of software support therefore affects the product’s value from the day it is purchased.

Its chronology also compresses a relatively short period between sale and the alleged loss of eligibility:

The filing says buyers could not prevent, postpone or opt out of Apple’s compatibility decision. It further alleges that Apple did not tell them, either before or at purchase, when eligibility for future major watchOS versions would end.

What “Software Support” Means Here—and What the Filing Leaves Blurry

Major operating-system releases can add features, maintain compatibility with newer phones and applications, improve performance and change how a device works. They are not necessarily the same thing as security patches, isolated bug fixes or limited maintenance releases.

That distinction is important because the complaint uses more than one formulation. It alleges that affected Watches will remain on watchOS 26 “with no further update.” Elsewhere, it focuses more specifically on permanent ineligibility for future major versions of watchOS.

The supplied document does not provide Apple’s official support policy, a compatibility list issued by Apple or a breakdown of whether security, bug-fix and application-compatibility updates would all end at the same time. It therefore does not establish from Apple’s own records precisely which categories of support will stop.

The legal theory does not require the plaintiff to pretend that software support and hardware condition are identical. It instead claims they are economically connected: working hardware may lose part of its value if the operating system, applications or paired phone continue evolving without it.

The Complaint Calls It “Bricking.” Its Evidence Describes a Risk.

The filing repeatedly uses the terms “software tethering” and “bricking.” Those are the plaintiff’s characterizations. No court or regulator has adopted them in the supplied record.

In ordinary technology usage, a “bricked” device is one rendered effectively unusable. The complaint predicts that unsupported Watches will accumulate bugs, slow down or eventually stop functioning. It also acknowledges that some may continue functioning, though allegedly with reduced compatibility or performance.

What the document does not contain is equally relevant. It provides no device tests, failure rates, security analysis, list of lost applications or documented example of an affected Watch that stopped operating because it could not install watchOS 27. Goetz alleges economic injury, but the complaint does not say his own Ultra had become a nonfunctional brick.

The filing’s strongest immediate allegation is not that every affected Watch is already dead. It is that buyers paid without being told when Apple could stop carrying their devices into the next major software generation.

That difference does not eliminate the claimed harm. It defines what must still be proved. The plaintiff would need evidence supporting the alleged loss of value and showing that the support decision shortened the Watches’ useful economic lives—not merely that a new operating-system version exists.

The FTC Material Is Context, Not a Finding Against Apple

The complaint leans on a November 2024 staff report from the Federal Trade Commission, the federal agency responsible for enforcing major consumer-protection laws. The report discussed connected products generally and the potential harm caused when manufacturers fail to disclose how long necessary software updates will continue.

The quoted passage explains circumstances that may create consumer-protection concerns. It does not say that every device cutoff is deceptive, and the supplied filing does not identify an FTC investigation, enforcement action or finding against Apple over watchOS 27.

The complaint also cites Consumer Reports for the broader concern that manufacturer control over software can limit a customer’s ability to fully own a connected product. Again, that material supplies policy context. It does not decide whether Apple made a legally enforceable promise to these purchasers.

What the Lawsuit Actually Claims

1. Breach of contract and the duty of good faith

The first claim says each Watch purchase created a contract that included both the hardware and the continuing software ecosystem necessary for the device to function as marketed. The complaint invokes the “implied covenant of good faith and fair dealing,” a duty the filing describes as preventing either side from unfairly interfering with the other side’s expected benefit from an agreement.

Goetz alleges that Apple violated that duty by exercising control over software support in a way that conflicted with buyers’ reasonable expectations. The unresolved question is whether the purchase agreement actually carried the support expectation alleged. The complaint does not quote an express promise that every named model would receive updates for a specified number of years.

2. California’s prohibition on unfair business practices

The second claim invokes California’s Unfair Competition Law. Goetz proceeds under its “unfair” category, arguing that the alleged injury was substantial, could not reasonably be avoided because Apple controlled the relevant information, and was not outweighed by a consumer or competitive benefit.

Those are the plaintiff’s arguments about how the statute should apply. The supplied record contains no ruling that Apple’s conduct was unfair, unlawful or otherwise actionable.

The requested remedies

The complaint asks for class certification, damages, restitution, disgorgement, declaratory relief, an injunction, legal fees and potentially punitive damages. In plain English, it asks the court to allow the case to proceed for a group, award money where legally supported, declare the parties’ rights and order appropriate changes to future conduct. Requesting those remedies does not mean the court will grant them.

The $5 Million Figure Is a Jurisdictional Allegation, Not an Award

The complaint invokes the Class Action Fairness Act, a federal law that can place large multistate or interstate class actions in federal court. It alleges that the proposed class has more than 100 members, that at least one member is a citizen of a different state from Apple and that the aggregate amount in controversy exceeds $5 million.

“Amount in controversy” means the value the plaintiff says is at stake for jurisdictional purposes. It is not a finding that the proposed class suffered $5 million in losses, and it is not a damages award.

The filing estimates, based on information and belief, that Apple sold hundreds of thousands or millions of affected models across the United States. But the proposed class described in the complaint is limited to California residents, and the document does not provide a verified count of qualifying California purchasers.

The Missing Side of the Record

The supplied source contains no response from Apple Inc. It does not state whether Apple disputes the model list, the description of future support, the claimed consumer expectations or the alleged economic harm.

It also does not provide Apple’s technical rationale for compatibility decisions. The complaint says manufacturers have an incentive to make consumers replace devices and describes Apple’s decision as intentional. It does not supply evidence establishing that Apple chose the cutoff to force replacement purchases. Assigning that motive as fact would go beyond the record.

The absence of a defense filing does not strengthen or weaken Apple’s eventual legal position. It simply means this document presents one side at the opening stage of litigation.

What a Legitimate Fix Looks Like

The complaint identifies a disclosure problem that can be addressed independently of who ultimately wins the lawsuit. A meaningful fix would let a buyer compare connected products based on expected support before paying for them.

Disclose a minimum support period at purchase

Manufacturers could state a date or minimum number of years during which each model will receive defined categories of software support. That information should be visible at the point of sale, not buried in a document a customer must locate later.

Separate different kinds of updates

A clear policy should distinguish major feature releases from security patches, compatibility maintenance and critical bug fixes. Saying only that a product is “supported” leaves consumers unable to tell which functions are protected and for how long.

Publish a transition plan

When a model leaves the current operating-system cycle, customers should receive a precise explanation of what will continue working, which updates will stop and whether paired phones or important applications will remain compatible.

Make the promise durable

A support commitment is useful only if customers can rely on it after purchase. Policies should identify what remedy is available if promised support ends early or advertised functions are materially lost.

What to Watch

What Remains Unresolved

The complaint turns an unstated support period into the central issue. Goetz says the price, marketing and nature of a premium connected watch created a reasonable expectation that major software eligibility would continue while the hardware remained in good condition. The document does not identify a written Apple promise setting that duration.

The court has not decided whether the alleged expectation became part of the purchase contract, whether Apple’s disclosures were inadequate, whether its update decision was unfair under California law or whether the proposed class experienced a common economic loss.

Nor does the supplied record settle the technical question behind the legal dispute: what these Watches will lose, when they will lose it and whether watchOS 26 can keep them secure and functionally compatible without access to future major versions. Those facts—not the word “bricking” by itself—will determine whether this case documents premature obsolescence or a disputed boundary in ordinary software support.