Halide co-founder is suing former partner Sebastiaan de With for taking source code to Apple

$150,000: Lux Optics co-founder Ben Sandofsky sued former partner Sebastiaan de With in California alleging de With improperly used more than $150,000 in Lux funds and took Lux source code when he joined Apple in late January after an alleged December 2025 firing for financial misconduct. Apple allegedly tried to acquire Lux last summer but the talks failed and it ultimately hired de With; de With's attorney denies the allegations and says Apple was unfairly dragged into the dispute. The case creates IP and governance risk for Lux and reputational/legal exposure for de With and could prompt limited scrutiny of Apple's recruitment/acquisition conduct.

Analysis

A personnel-related legal headline involving transfer-of-knowledge risks elevates the due-diligence and indemnity premium for large tech firms sourcing features via external hires. Expect acquirers to increase escrow/reserve demands and extend IP audits, which should compress implied valuations for small developer targets by ~10–20% and add 3–6 months to typical integration timetables.

On product cadence, disputes around proprietary tooling embed a non-trivial timing risk: software features that rely on small-team expertise are the easiest to delay and the hardest to replicate in-house quickly, pushing meaningful feature delivery out by a single flagship cycle (6–12 months) rather than being lost permanently. That timing slippage disproportionately impacts upgrade levers that drive marginal hardware ASPs and adjacent services monetization in a near-term window.

Competitively, a transient pause in a dominant player’s feature rollout creates a clear opening for Android incumbents and component suppliers aligned to them to capture share of incremental demand; sensor and ISP vendors could see order rebalancing within 3–9 months. The legal tail is asymmetric but low probability: an injunction is unlikely, yet the headline risk increases short-term implied volatility and raises recruiting friction for hires from small shops.

Contrarian read: the balance sheet and product pipeline of the dominant platform remain robust; headlines are more likely to cause ephemeral volatility than fundamental share loss. Tactical weakness ahead of the next product cycle offers a buy-the-dip entry for patient, event-aware investors rather than a long-term structural short.

Key Decisions for Investors

• Pair trade (3–6 months): Short AAPL notional vs Long GOOGL notional sized to neutralize beta — objective capture of feature cadence divergence. Target entry on >2% intra-day weakness in AAPL vs market; take profit at 3–6% relative move. Risk: Apple executes internal roadmap; set stop if AAPL outperforms by 4% absolute.
• Hedge for AAPL holders (1–3 months): Buy 3-month 5% OTM protective puts to cap short-term headline-driven downside while retaining upside into the next product event. Expect to pay a premium roughly equivalent to a low-single-digit percent of position value; treat as insurance rather than directional bet.
• Event volatility trade (0–2 months): Buy short-dated AAPL call or put straddle around major news flow windows to monetize elevated implied volatility from legal headlines — close within 2–10 trading days post-news to avoid theta decay. Risk: implied vol collapses if story fades; size small relative to portfolio.
• Opportunistic long (3–9 months): If AAPL weakness >5% and fundamentals hold, accumulate into strength ahead of the next product cycle with a 6–12 month horizon. Reward: asymmetric upside from product re-acceleration; risk: slower-than-expected feature recovery — cap exposure to single-digit percent of tech allocation.