Apple flirted with Halide to upgrade its Camera app—and then walked away

Apple flirted with Halide to upgrade its Camera app—and then walked away. In the summer of 2025, the iPhone maker held acquisition talks with Lux Optics—the small team behind the Halide camera app and related software—only to pull back in September, according to reporting summarized by Engadget from The Information. The move would have been a marquee shortcut for Apple to bolt pro-grade software onto its iPhone hardware, potentially smoothing the path toward more advanced capture controls on future models.

Lux Optics is known in the pro-photography crowd for Halide, a third-party app celebrated for tactile, manual controls, RAW workflows and a more granular, professional feel than stock iOS. Apple’s interest wasn’t just about lending polish to a camera app; the talks, if they had closed, could have given Apple a way to accelerate features that align with hardware ambitions—one of many rumors around a likely “variable aperture” direction for the upcoming iPhone 18 Pro line. The theory was that Halide’s engineering playbook—precise exposure, focus, and color management—could be folded into Apple’s own Camera app without a decade of in-house trial and error.

Yet the talks ended in September 2025, and the court of public interpretation kept moving. The Information, cited by Engadget, notes that Lux Optics’ co-founders, Ben Sandofsky and Sebastiaan de With, decided the potential future value of Halide would grow with time, and they chose not to proceed with Apple’s overture. The decision coincided with a dramatic twist in Lux Optics’ internal saga: a lawsuit between the co-founders over how company funds were used during the talks. The timeline makes for a messy but instructive window into how big tech and small software studios negotiate value, talent, and IP when hardware plays a central role.

What if Apple had pulled the deal off? For consumers, the promise would have been a more seamless blend between elite manual controls and the iPhone’s computational pipeline—a combination that could push the built-in Camera app closer to the kind of control power professionals rely on today. For enthusiasts, it would be a reminder that even a closed ecosystem sometimes leans on external software sensibilities to drive the ultimate user experience. But the fact that Apple chose not to close the deal also underscores a crucial truth: Apple’s path to feature leadership in camera software often runs through internal teams and tightly controlled integration, not just through acquiring specialized apps.

From a practitioner perspective, there are a few takeaways. First, acquisitions of software-brushfire talent remain a high-stakes tactic for tech giants seeking rapid feature parity with hardware. Second, the integration hurdle is real: even if a deal closes, stitching Halide’s user interface and processing logic into iOS would require careful alignment with Apple’s design language, performance budgets and privacy safeguards. Third, the case highlights talent mobility risks for niche studios—borderline catalysts for innovation on one hand, and flashpoints for internal disputes on the other. Fourth, the episode signals how Apple weighs long-term strategic value against near-term talent leverage: the company may prefer to develop rival capabilities in-house or acquire quietly later, rather than absorb a contentious acquisition that could distract from other flagship projects.

The episode remains a telling snapshot of how Apple balances hardware ambitions with software ambitions in a way that shapes what everyday users see in their pockets. While Halide’s team remains an independent force in mobile photography, Apple’s broader strategy for camera software appears to lean more on internal development and carefully chosen partnerships than on a single, transformative acquisition—at least for now.

Sources

Apple considered buying Halide to upgrade its native Camera app