Court Adds Craig Federighi to xAI Antitrust Case – Implications for iOS Development

Apple’s senior vice president of software engineering, Craig Federighi, has been named a document custodian in the antitrust lawsuit filed by Elon Musk’s xAI against Apple and OpenAI. The court’s decision stops short of pulling in CEO Tim Cook, but it signals that the litigation will scrutinize the software‑engineering choices behind Apple’s recent AI push. For developers who maintain iOS apps, the ruling raises several concrete questions about SDK versions, App Store ranking signals, and the future of Apple Intelligence.

---

1. The update – what the court actually ordered

• Custodian designation – The magistrate judge granted xAI’s request to add Federighi as a custodian, requiring Apple to turn over any relevant documents in his possession by June 17 2026.
• Cook excluded – The same request for Tim Cook was denied because the plaintiffs did not show that Cook holds unique evidence beyond what has already been produced.
• Scope of discovery – Apple must also provide documents related to its partnership with Google that mention any exclusivity clauses for AI providers, again by June 17 2026.
• Other requests denied – The court rejected demands for internal AI policy documents and for an unnamed employee’s iPhone‑sales data, deeming them outside the case’s core claims.

The decision is fully available on the U.S. District Court docket.

---

2. Why this matters to iOS developers

a. Apple Intelligence and Siri integration

Apple’s Apple Intelligence framework, introduced in iOS 18, bundles on‑device LLM capabilities with Siri. The lawsuit alleges that Apple’s agreement with OpenAI influences App Store rankings, potentially giving “AI‑enhanced” apps an unfair boost. If the court later finds that Apple used software‑engineering decisions to favor certain apps, developers could see:

• Changes to ranking algorithms – Apple may be forced to disclose or adjust the weight given to AI features in search results.
• New compliance requirements – Apps that call the AppleIntelligence APIs might need to disclose the model version they are using (e.g., OpenAI‑based vs. on‑device) to satisfy transparency rules.

b. SDK versioning and deprecation risk

Apple typically rolls out new AI‑related APIs in the latest SDK and deprecates older ones after two major releases. If the litigation leads to a rollback or a pause on certain APIs, developers could face:

1. Delayed migration from IntelligenceKit (iOS 18) to the upcoming IntelligenceKitV2 slated for iOS 19.
2. Extended support windows for the older SiriKit extensions, as Apple may need to keep them functional for longer than the usual 5‑year support cycle.

Keeping an eye on the Apple Developer Documentation will be essential to adjust build pipelines accordingly.

c. App Store Review Guidelines

The App Store Review Guidelines already require developers to be truthful about AI usage (section 5.2). A court‑ordered disclosure could tighten those rules, for example:

• Requiring a metadata field that lists the AI provider (OpenAI, Anthropic, etc.).
• Mandating that any ranking‑related metadata (e.g., "AI‑enhanced" badge) be backed by verifiable evidence.

Developers should start preparing a compliance checklist now, adding a step to verify AI‑related metadata before each submission.

---

3. Migration path – what to do today

Action	Why	How
Audit AI calls	Identify which parts of your app rely on Apple Intelligence or third‑party LLMs.	Search your codebase for IntelligenceKit, SiriKit, and any OpenAI SDK imports. Generate a report with grep -r "IntelligenceKit" .
Lock SDK versions	Prevent accidental adoption of a future API that might be impacted by the case.	In Xcode, set the IPHONEOS_DEPLOYMENT_TARGET to iOS 18 and add a Podfile entry pod 'IntelligenceKit', '~> 1.0'
Add metadata fields	Prepare for possible new App Store requirements.	Update your Info.plist with a custom key AIProvider and include it in the App Store Connect metadata screen.
Monitor court filings	Stay ahead of any rulings that affect ranking or API usage.	Subscribe to the docket via PACER or set up a Google Alert for “xAI Apple OpenAI lawsuit”.
Test on‑device fallback	Ensure your app still works if the cloud‑based model is restricted.	Implement a local fallback using CoreML models that replicate essential features of the cloud LLM.

---

4. Broader cross‑platform considerations

While the case is centered on Apple, the super‑app market that xAI mentions includes Android ecosystems that also host AI‑enhanced applications. Developers who ship on both platforms should:

• Review the Google Play Developer Policy for AI disclosure (section 4.5) to keep parity with Apple’s potential new rules.
• Keep the Kotlin Multiplatform Mobile (KMM) or Flutter code paths aligned, so that any changes to AI‑related metadata can be applied in a single place.
• Consider abstracting AI provider logic behind an interface, allowing you to swap OpenAI, Anthropic, or on‑device models without touching platform‑specific UI code.

---

5. Looking ahead

The court’s decision does not yet dictate any changes to the App Store or to Apple’s AI partnerships, but it opens the door for deeper discovery into how Apple engineers—specifically Federighi—handled the integration of OpenAI models. Developers should treat the next six months as a period of heightened scrutiny:

• Watch for updated guidelines from Apple’s Review Team.
• Prepare for possible audits of AI usage in your app.
• Stay flexible with SDK versions to avoid forced migrations.

By taking these steps now, you can keep your app compliant, maintain its ranking, and avoid surprises when the litigation reaches a final resolution.

---

*For a full copy of the court’s order, see the government docket link.*