Browserenginekit

If you're building a browser with a non-WebKit engine for iOS in the EU or Japan, this is the framework you'll need to wrangle process isolation, XPC communication between your web content, networking, and rendering extensions, and all the system integration Apple requires. It covers the mandatory entitlement dance (you'll need approval from Apple), eligibility checking via BrowserKit, and how to coordinate Metal rendering, text interaction, and downloads across sandboxed processes. The architecture is strict: host app launches extensions, no extension-to-extension launching, everything talks through brokered XPC endpoints. Worth noting that embedded engines for non-browser apps use different entitlements and can't use JIT. This is specialized infrastructure, not something you casually drop into a project.