What problem does it solve?
BrowserEngineKit helps you develop and ship non-WebKit browser engines on iOS and iPadOS while correctly handling process isolation, entitlements, eligibility checks, and cross-process coordination.
Core Features & Use Cases
- Eligibility first for EU alternative engines: Use BrowserKit’s BEAvailability to determine whether the current device can run an alternative browser engine without hard-coded region logic.
- Process-isolated browser architecture: Orchestrate host, web content, networking, and rendering via XPC with least-privilege boundaries.
- Production-grade entitlements and security guidance: Configure host and extension entitlements, apply the restricted sandbox, manage JIT requirements, and follow arm64e distribution constraints.
- Practical integration patterns: Host/display rendering layers, coordinate atomic layer transactions, and implement text interaction and download monitoring workflows.
Quick Start
Implement a BrowserEngineKit host app that checks device eligibility with BEAvailability, launches the required extension processes, and brokers XPC endpoints so the web content extension can connect to networking and rendering.