In the spring of 2025, Apple extended its default app controls beyond mail and browsers to include translation, opening the door for third‑party tools to supplant Apple Translate. DeepL was first out of the gate, announcing on 24 April 2025 that users running iOS 18.2 or later can now select DeepL as their default translator directly in Settings. Under the hood, developers must integrate a bona fide translation engine, declare a new entitlement, provide a Translation UI Provider extension, and embed a minimal SwiftUI scene—steps clearly documented on Apple’s developer portal. While DeepL leads, Google Translate, Microsoft Translator, iTranslate and others are expected to follow as the ecosystem evolves.
What Changed in iOS 18
iOS 18.2, released December 2024, introduced a centralized “Default Apps” hub in Settings, initially for email, messaging, browser and calling apps. In Spring 2025, Apple expanded this feature in iOS 18.4 to include navigation for EU users and translation apps worldwide, fully democratizing the default‑app model.
DeepL Takes the Lead
DeepL’s announcement on X and Facebook confirmed that its latest version meets Apple’s extension requirements and appears under Settings → Apps → Default Apps → Translation. DeepL users on iOS 18.2+ can now invoke DeepL via Siri, share sheets, and any context‑menu Translate command without extra taps.
Developer Requirements to Become Default
Apple’s Translation UI Provider documentation outlines four mandatory steps for any translation app:
1. Genuine Translation Engine
Your app must perform real translations—either via an on‑device model or a cloud‑based API—to satisfy the system’s expectations for quality and privacy.
2. Entitlement Declaration
Add the com.apple.developer.translation-app entitlement to your app’s .entitlements file so iOS can list it among Default Apps → Translation.
3. Translation UI Provider Extension
Implement an app extension conforming to the Translation UI Provider framework. This grants system permission for network lookups and ties your engine into the OS’s translation pipeline.
4. Minimal SwiftUI Scene
Embed a lightweight SwiftUI view—about 40 lines of sample code—to present translations in a native interface whenever the user invokes “Translate”.
How Users Can Switch
To choose a new default translator, navigate on iPhone or iPad to Settings → Apps → Default Apps → Translation, then select from the list of compliant apps. After selection, some apps may prompt additional setup—follow any on‑screen instructions to complete the integration.
What’s Next for Other Apps
Google Translate currently does not support this feature, so it won’t appear in the Default Apps menu yet. Likewise, Microsoft Translator and iTranslate will need to add the new entitlement and extension before they can compete as the default. Given the straightforward integration path, expect a wave of updates from every major player racing to claim that coveted slot.
Conclusion
With iOS 18’s Default Apps expansion, Apple has handed translation‑app developers a rare opportunity to own one of the most‑used system functions. By meeting the four clear requirements—real engine, entitlement, UI Provider extension, and SwiftUI scene—any translation app can join DeepL in the Default Apps list. As the ecosystem reacts, users will enjoy richer, more specialised translation experiences at the system level, further blurring the lines between built‑in and third‑party services.