It has emerged that Apple explored acquiring Lux Optics, the company behind the iPhone camera app "Halide," in the summer of 2025—a revelation that surfaced through a lawsuit between the app's co-founders. According to a report by The Information, Apple was reportedly focused on enhancing its standard camera app ahead of the iPhone 18 Pro generation.
What makes this story notable is that it goes beyond mere acquisition speculation. Lux co-founder Ben Sandofsky alleges in a court filing that fellow co-founder Sebastiaan de With misappropriated company funds for personal use and, further, took Lux's confidential materials and source code to Apple. De With's side has denied these claims, countering that the lawsuit is retaliatory in nature.
At this point, Apple is not a defendant, and no wrongdoing has been established against it. Still, this episode offers meaningful insight into where Apple is trying to differentiate the iPhone's camera competitiveness. It suggests Apple may be looking to redesign not just hardware improvements, but the entire software experience that puts that hardware to use.
What drew Apple's interest was the camera app's control interface itself
According to the report, the reason Apple took interest in Lux Optics is relatively clear. Halide is known as an app that offers finer manual control over the iPhone's camera, and Lux has also developed Kino for video shooting, Spectre for long-exposure photography, and Orion, which turns an iPad into an external HDMI monitor. It's a development company that has continuously refined mobile production software extending well beyond the shooting experience itself.
The Information's report suggests that Apple anticipated the iPhone 18 Pro's camera would approach professional-grade equipment in certain advanced features, and wanted to revisit its standard camera app accordingly. The current stock camera app is designed with an emphasis on basic operation, and users seeking fine manual adjustments or specific shooting workflows often turn to third-party apps instead. If this pattern continues, the value Apple invests in camera hardware improvements may not be fully conveyed through its native software alone.
In that sense, the reported consideration of acquiring Halide's maker makes sense. It seems more plausible that what Apple wanted wasn't the app itself, but rather the know-how and intellectual property behind how to redesign the shooting experience for premium iPhones. Had Apple successfully absorbed Lux, it might have been able to expand the standard camera app's capabilities in less time than building everything from scratch.
What's at stake isn't the hardware, but the design that puts hardware to use
Smartphone camera competition has long been discussed in terms of straightforward metrics like sensors, zoom, and low-light performance. But as performance gaps between flagship models narrow, the next differentiator becomes depth of control and shooting workflow. This matters because it's important for the experience to be easy for beginners while still allowing advanced users to instantly access the adjustments they need.
This report can be read as evidence supporting that shift. The fact that Apple reportedly took interest in Lux's intellectual property indicates that the competitive axis of cameras is expanding from hardware alone to encompass software design and UI as well. The specific details of the iPhone 18 Pro remain unconfirmed ahead of an official announcement, but multiple reports agree on the general direction: that Apple views software as a priority issue.
Acquisition talks ended in September 2025, and the conflict surfaced afterward
According to the report, acquisition talks between Apple and Lux took place in the summer of 2025 and ended without a deal in September of that year. The reported reason is that Sandofsky and de With believed Lux's enterprise value could be raised further through future updates to Halide. Whether they were dissatisfied with Apple's terms or judged that remaining independent would be more advantageous isn't clear in detail. At the very least, though, Lux at the time had decided not to rush a sale.
What followed happened quickly. Sandofsky reportedly began investigating de With's use of company funds in October 2025, placed him on leave, and then terminated him in December. Then, in January 2026, de With announced he had joined Apple's design team. The acquisition never went through, but one of the co-founders ended up moving to Apple anyway.
That said, it would be risky to draw firm conclusions about Apple's intentions from this timeline alone. What can be confirmed at this point is simply that acquisition talks took place, that a conflict between the co-founders subsequently went to court, and that de With moved to Apple. It cannot be definitively stated that Apple, having failed to acquire all of Lux, pivoted to a talent-acquisition strategy instead.
What the lawsuit questions isn't so much Apple's responsibility as Lux's governance
The most serious point of contention in the lawsuit is Sandofsky's claim that de With used over $150,000 in company funds for personal expenses since 2022. The suit further alleges that de With took confidential materials and source code related to Lux's future features to Apple. That said, what's being presented here are merely the plaintiff's allegations, not established facts.
De With's side denies ever using, transferring, or disclosing Lux's intellectual property. It also claims the lawsuit came in retaliation for de With's request to access Lux's financial records. In other words, the structure here is: one side alleges misappropriation of funds and leaking of confidential information, while the other frames it as retaliation for pursuing accounting questions.
Reading this without sorting out these points risks leaving only the impression that Apple improperly absorbed Halide's technology. But what's actually more certain from this news is not so much Apple's acquisition consideration as the fact that Lux's management and governance had rapidly destabilized. At small app development companies, when trust between co-founders breaks down, the organization often falters before the product does. That fragility has been exposed through this lawsuit.
The redesign of the native camera experience has already begun
What matters to Apple isn't simply whether it could actually acquire Lux. What's significant is that Apple was reportedly considering such an acquisition at all—a sign of how strongly it felt the need to raise the completeness of its native camera app. As the price and performance of premium iPhones climb, if the native app remains limited to basic operations, Apple risks ceding the initiative on differentiation to third-party apps.
Apps like Halide aren't merely supplementary add-ons existing outside the native experience—they represent demand that the native software has yet to capture, given tangible form ahead of time. The fact that Apple showed interest in its developer indicates that the third-party market isn't just a peripheral industry, but a gauge of where native software falls short. Underlying this is a shift in the iPhone camera experience, moving from simply "being able to take photos" toward "how those capabilities can be selectively used."
There are two focal points going forward. One is how far Apple will incorporate advanced manual controls and professional-grade workflows as standard features in future iPhones. The other is where room will remain for dedicated apps like Halide even so. If Apple significantly expands its native camera app, third-party developers will need to seek out sharper, more specialized functions and roles suited to production workflows. This lawsuit story has spread with attention-grabbing headlines, but what truly matters for the industry is that iPhone camera competition is entering a phase that can no longer be measured by hardware comparisons alone.
Sources