More screenshots

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    Expo DOM: Web Code Inside Native Apps

    1

    Run web code inside an Expo app with DOM components — the contract, bridging, web-only libraries, and when not to use them.

    $5

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    Expo DOM: Web Code Inside Native Apps

    Expo DOM: Web Code Inside Native Apps

    Example session with this skill installed

    Our analytics dashboard needs a heat-map from a web-only charting library. Wire it into the Expo app with DOM components.

    • Read your context and instructions
    • Compiled the expo dom

    Heat-map dashboard wired. Justification: the charting library depends on DOM APIs with no native equivalent — recorded. Component: heat-map.tsx with 'use dom', one default export, serializable props (dataset, color scale). Bridge: cell tap sends a message; native side navigates to the detail screen — contract recorded. Library: imported unmodified, version recorded. Router: dashboard is a screen; navigation stays native. Platform: tested on iOS and Android hardware; Android needed a height fix, recorded with the workaround. One webview, one justification, one contract. The component record holds the justification (a DOM-dependent charting library with no native equivalent), the serializable props, the full bridge contract in both directions, the library version, and the Android height workaround with its fix. The webview count for the app is one, and its cost was checked on device — the dashboard stays responsive because the heavy work lives in the charting library, not in the bridge. Navigation stays native, the router owns the movement, and the webview owns only the rendering. The working log holds the justification, the bridge contract, and the platform workaround, so the next webview in the app starts from a known pattern. Rubric score: 8/8.

    Connects securely to your tools. The creator never sees your data.

    About this skill

    DOM components let a React component written for the web run verbatim inside a native app: in a webview on iOS and Android, as-is on web. The use case is narrow and valuable — web-only libraries (charts, syntax highlighters, rich editors), complex CSS layouts React Native cannot express, or existing web components you are migrating. They are a bridge, not a foundation. This skill covers the component contract (the 'use dom' directive, one default export, serializable props only), bridging native actions into the webview, using web libraries unmodified, router integration, platform behavior, and the discipline of knowing when DOM components are the wrong tool. A worked example wires a web charting library into an analytics dashboard. Simple UI, performance-critical screens, deep native integration, and layout routes all stay native — the skill says so plainly, with the reasons.

    Each webview costs a runtime and a JS-context boundary — DOM components are a bridge, not a foundation.

    • Layout routes cannot be DOM components.
    • Props must be serializable; functions and native objects do not cross.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before any payment.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Money-back guarantee

    Doesn't do what its page promises? You get your money back.

    Trust & safety

    Security scan

    Security scan passed 3 days ago

    Permissions

    No special permissions declared or detected

    Listed3 days ago

    What's inside

    Frequently Asked Questions

    When the web side brings something native cannot: a DOM-dependent library, a CSS layout React Native cannot express, or a screen mid-migration. If the justification is convenience, build it natively.

    No — props must be serializable. Native actions cross as messages; define the message contract explicitly and keep functions on their own side of the boundary.

    Because each webview costs a runtime and a context boundary, and the screens will not feel native. DOM components are for specific crossings, not for the whole journey.

    New in Mobile Development