← ClaudeAtlas

browserenginekitlisted

Build alternative browser engines using BrowserEngineKit. Use when developing a non-WebKit browser engine for iOS/iPadOS in supported regions, managing web content/rendering/networking extension processes, configuring GPU and networking process capabilities, checking alternative-engine device eligibility, or reviewing BrowserEngineKit entitlements and Info.plist setup.
thienqo/ios-skills · ★ 11 · Web & Frontend · score 69
Install: claude install-skill thienqo/ios-skills
# BrowserEngineKit Framework for building web browsers with alternative (non-WebKit) rendering engines on iOS and iPadOS. Provides process isolation, XPC communication, capability management, and system integration for browser apps that implement their own HTML/CSS/JavaScript engine. Examples target Swift 6.4 and current Apple SDKs. BrowserEngineKit is a specialized framework. Alternative browser engines are available only through Apple-approved entitlement profiles and supported-region device eligibility. EU support applies to eligible users on iOS 17.4+ and iPadOS 18+; Japan support starts with iOS 26.2 and adds explicit PAC/MIE security requirements for browser apps. Development and testing can occur anywhere. The companion frameworks BrowserEngineCore (low-level primitives) and BrowserKit (eligibility checks, data transfer) support the overall workflow. ## Contents - [Workflow](#workflow) - [Route by Task](#route-by-task) - [Core Decisions](#core-decisions) - [Common Mistakes](#common-mistakes) - [Review Checklist](#review-checklist) - [References](#references) ## Workflow 1. Verify regional eligibility, default-browser requirements, device capability, and approved entitlements before implementation. 2. Model the host plus web-content, networking, and rendering extensions and follow the required bootstrap order. 3. Create, retain, invalidate, and reconnect extension processes/XPC channels as explicit lifecycle states. 4. Request only the capabilities each extension