browserenginekit

Build multi-process iOS browser engines with XPC communication and isolated extensions.

Updated Apr 30, 2026
One-click install
npx skills add https://github.com/onymchat/onym-ios --skill browserenginekit-onymchat
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: browserenginekit
Source: https://github.com/onymchat/onym-ios/tree/main/.claude/skills/browserenginekit
Command: npx skills add https://github.com/onymchat/onym-ios --skill browserenginekit-onymchat

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

BrowserEngineKit provides a complete framework for building alternative (non-WebKit) browser engines on iOS, delivering process isolation, XPC communication, capability management, and system integration to support custom HTML/CSS/JS rendering within a sandboxed host app.

Core Features & Use Cases

  • Multi-process architecture with Host, Web Content, Networking, and Rendering extensions
  • Entitlements guidance and architecture patterns across BrowserEngineKit, BrowserEngineCore, and BrowserKit
  • Layer hosting, text interaction, accessibility, and memory management for custom engines
  • Use cases include EU-distributed engines requiring eligibility checks, secure sandboxes, and per-extension lifecycle coordination

Quick Start

Set up a host app to launch the three extension processes (content, networking, rendering) and bootstrap XPC communication using BrowserEngineKit APIs.

Frequently Asked Questions about browserenginekit

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I build a non-WebKit browser engine on iOS?▼

Building a non-WebKit browser engine on iOS requires a multi-process framework providing process isolation, XPC communication, and layer-hosted rendering across host, content, networking, and rendering extensions within a sandboxed host app.

What is the architecture for process isolation in an iOS browser engine?▼

The architecture for iOS browser engine process isolation uses separate Host, Web Content, Networking, and Rendering extensions, coordinating lifecycle and capabilities through BrowserEngineKit, BrowserEngineCore, and BrowserKit.

How do I set up XPC communication for custom iOS browser extensions?▼

You set up XPC communication for custom iOS browser extensions by configuring a host app to launch content, networking, and rendering processes, then bootstrapping the XPC connections using BrowserEngineKit APIs.

Can I use layer-hosted rendering for a custom HTML engine on iOS?▼

Yes, you can use layer-hosted rendering for a custom HTML engine on iOS. The framework provides layer hosting, text interaction, accessibility, and memory management capabilities specifically for custom engines.

Do I need specific entitlements for alternative browser engines distributed in the EU?▼

Yes, alternative browser engines distributed in the EU require specific entitlements guidance and eligibility checks to enforce secure sandboxes and proper per-extension lifecycle coordination.

Why does my iOS browser engine need a sandboxed host app?▼

An iOS browser engine needs a sandboxed host app to enforce architecture patterns and security constraints, ensuring isolated processes handle custom HTML, CSS, and JS rendering safely.