Halide's Bitter Split: When Apple Poaches a Co-Founder, the Code Goes With Him

Sebastiaan de With built something rare in the App Store economy: a photography app that people actually loved. Halide, the flagship product of Lux Optics, earned a devoted following among iPhone photographers who wanted manual controls, RAW capture, and a tactile interface that felt nothing like the sterile defaults Apple shipped. When de With quietly joined Apple in late January 2025, many in the indie developer community saw it as a kind of validation. Now, his former co-founder is suing him, and the dispute cuts to one of the most uncomfortable questions in software: when a developer walks out the door, what exactly walks with them?

According to the source reporting, Lux Optics co-founder Ben Sandofsky has filed suit against de With, alleging that de With brought Halide's source code with him when he joined Apple. Apple had previously attempted to acquire Lux Optics outright before ultimately hiring de With individually. That backstory matters enormously. It means Apple knew exactly what it was getting, had already assessed the value of the underlying technology, and then chose a different path to access that talent and, allegedly, that code.

Founder disputes are not unusual in the startup world, but they carry a particular sting in small two-person shops where the division of labor is intimate and the intellectual property is deeply intertwined with individual identity. Halide was not a product built by a team of fifty engineers with clean handoff documentation. It was the creative output of two people who spent years making deliberate, opinionated decisions about how photography software should feel. When one of those people leaves, the question of what belongs to the company versus what lives in a developer's head becomes genuinely difficult to answer.

Source code, however, is not a gray area. Unlike general knowledge, skills, or professional instincts, source code is a specific, copyrightable artifact. If de With copied or transferred Halide's proprietary codebase to Apple, that would represent a concrete act of misappropriation rather than the murkier territory of trade secrets embedded in memory. Sandofsky's lawsuit, if the allegations hold, is not about punishing someone for being talented. It is about the most fundamental protection a small software company has: ownership of what it built.

The broader context here is a power asymmetry that the App Store era has made structurally routine. Apple is simultaneously the platform, the distributor, the hardware manufacturer, and now, apparently, a competitor willing to hire the people who built the most interesting things on top of its own ecosystem. Halide succeeded in part because it pushed iPhone camera hardware to its limits in ways Apple's own Camera app did not. That is precisely the kind of institutional knowledge Apple would want inside its walls.

The chilling effect this case could send through the indie developer community is hard to overstate. Small studios building on Apple's platform have always operated under a quiet tension: their success depends entirely on Apple's goodwill, API access, and App Store placement, while Apple retains the ability to replicate, acquire, or absorb whatever proves most compelling. The Halide situation makes that tension explicit and adversarial in a way that a simple acquisition would not have.

If it becomes understood that Apple can hire one half of a two-person studio and potentially gain access to years of proprietary development work, the rational response for any small developer is to restructure IP agreements, add non-compete and non-solicitation clauses with real teeth, and treat every employee or partner as a potential vector for competitive exposure. That is a significant administrative and legal burden for studios that often operate with no HR function and handshake-level trust between founders.

There is also a subtler feedback loop worth watching. Developers who feel exposed by this dynamic may become less willing to build deeply innovative tools on Apple's platform, preferring instead to keep their most valuable work on platforms where Apple is not also the landlord, the talent scout, and the potential acquirer. The App Store's vitality has always depended on independent developers taking creative risks. Cases like this one quietly raise the cost of doing so.

Sandofsky's lawsuit is still in its early stages, and the full facts remain contested. But regardless of how it resolves, the dispute has already done something the legal system rarely manages: it has made visible a structural vulnerability that thousands of small developers share, and it has attached a name, a product, and a story to it.

The next generation of indie developers building the next Halide will be watching the outcome very carefully.