Apple isn't opposing Jon Prosser's bid to reopen his defense in the lawsuit over the leaked iOS 26 Liquid Glass redesign. A judge still has to sign off, but the stipulation could give the leaker his first real chance to contest Apple's claims.
Jon Prosser, the leaker at the center of Apple's lawsuit over the early reveal of the Liquid Glass interface, may get another chance to formally answer the complaint. In a court filing made public on June 10, Apple and Prosser jointly asked Judge James Donato to set aside the default that was entered against him last October. Apple is not opposing the request, though the judge still has to approve it before anything changes.

What the case is actually about
This is a legal story with a development angle baked into it. Last year, Apple sued Prosser over the leak of Liquid Glass, the visual overhaul that shipped as the headline change in iOS 26. Apple also named Michael Ramacciotti in the suit. According to Apple's court documents, Ramacciotti secretly accessed an iPhone belonging to Apple employee Ethan Lipnick, then got paid for showing Prosser a build of iOS 26 that was still in active development. Lipnick was later fired.
For anyone who builds or maintains apps across iOS and Android, the underlying detail matters more than the courtroom drama. Pre-release OS builds carry unfinished APIs, private frameworks, and design language that Apple has not committed to. Liquid Glass changed how layering, translucency, and material rendering behave across the system, which has real downstream effects on custom UI, blur effects, and any view hierarchy that leaned on the older material system. A leaked early build shows none of the eventual stability or final behavior, which is exactly why Apple guards these images so tightly.
How the case got to a default
Apple's filings say Ramacciotti cooperated with the lawsuit from the start, while Prosser missed several deadlines to respond to the complaint. Prosser disputed that account. Regardless of the disagreement, the court granted Apple's request for an entry of default last October after Prosser failed to answer by the deadline. A default effectively forfeits the right to contest the allegations, putting a defendant on the path to losing without ever arguing the merits.
The situation shifted on April 15. Two days after Apple and Ramacciotti filed a joint status report, Prosser's newly retained attorney filed a separate report. The attorney said he had been hired two days earlier and signaled that Prosser intended to move quickly to vacate the default by presenting "evidence of meritorious defenses to Apple's claims."
The stipulation
That intent became a formal agreement in the document filed this week. Apple and Prosser told the court they jointly want the default set aside. Apple's reasoning, quoted from the filing, ties the decision to efficiency:
WHEREAS, in light of Mr. Prosser's recent retention of counsel and agreement to immediately produce discovery, Apple believes setting aside the entry of default is the most efficient way to advance this case without further delay, and Apple does not oppose setting aside the entry of default.
In plain terms, Prosser agreed to immediately produce discovery, and in exchange Apple is willing to let him reenter the case as an active participant rather than collect a default win. That is a practical move. A default judgment against a defendant who later surfaces with counsel and evidence often invites appeals and procedural fights, so advancing on the merits can be cleaner for the plaintiff.

The key caveat: Apple not opposing the request is not the same as the request being granted. Judge Donato still has to confirm the stipulation before the default is formally set aside. Stipulations like this are commonly approved, but the court retains discretion.
Why developers should keep half an eye on this
The outcome here won't change anyone's build settings, but it sets a marker for how aggressively Apple pursues leaks tied to its development pipeline. The company has historically used confidentiality agreements and internal controls to keep unreleased software contained. A lawsuit that reaches into the chain of how a build moved from an employee's phone to a public reveal is a signal about how far Apple will go when that containment fails.
For the wider community that tracks iOS and Android release cycles, leaks remain an unreliable basis for planning real work. Final APIs, deprecations, and behavior changes only become dependable once Apple ships beta seeds through official channels and publishes release notes. Building against anything earlier means building against something that may not exist by the time the OS ships.
The case continues, and the next move belongs to Judge Donato. If he confirms the stipulation, Prosser gets the chance he has been seeking to actually argue the allegations rather than lose by default.

Comments
Please log in or register to join the discussion