CommunityProgramación y desarrollogithub.com

expo/use-dom

Utiliza componentes DOM de Expo para ejecutar código web en una webview en dispositivos nativos y tal cual en la web. Migra código web a nativo de forma incremental.

¿Qué es use-dom?

La habilidad `expo/use-dom` permite a los desarrolladores ejecutar código web (HTML, CSS y JavaScript) dentro de una vista web en plataformas nativas (iOS/Android) y directamente en la web, utilizando componentes DOM de Expo. Esto facilita la migración gradual de aplicaciones web a nativas sin necesidad de reescribir todo el código desde cero. Es compatible con Expo SDK 50+ y se integra con frameworks como React Native y Expo Router. Al envolver componentes web en un contenedor DOM, se mantiene la interactividad y el estilo original, mientras que se aprovechan las capacidades nativas de forma progresiva. Es especialmente útil para proyectos que desean incorporar funcionalidades web existentes en una aplicación nativa de manera modular.

Compatible con~Claude Code~Codex CLI~Cursor
npx skills add https://github.com/expo/skills/tree/main/skills/use-dom

Installed? Explore more Programación y desarrollo skills: steipete/bluebubbles, steipete/eightctl, steipete/blucli · View all 6 →

Preguntar en tu IA favorita

Abre un nuevo chat con esta habilidad de agente ya precargada.

Documentación

¿Qué hace use-dom?

Utiliza componentes DOM de Expo para ejecutar código web en una webview en dispositivos nativos y tal cual en la web. Migra código web a nativo de forma incremental.

¿Qué es expo/use-dom?

expo/use-dom es una habilidad que te permite ejecutar componentes web existentes en un entorno nativo mediante una vista web (webview). En la web, estos componentes se renderizan directamente como HTML normal, mientras que en iOS/Android se ejecutan dentro de un contenedor WebView. Esto te permite reutilizar librerías, lógica o interfaces web sin necesidad de reescribir todo el código.

¿Cómo funciona?

Para usar expo/use-dom, envuelves un componente web en un contenedor especial que Expo proporciona. Este contenedor se encarga de:

  • En la web: Renderizar el componente directamente como HTML, sin cambios.
  • En nativo: Ejecutar el componente dentro de una WebView, manteniendo toda la interactividad, estilos y scripts originales.

El componente se comunica con la app nativa mediante un puente, permitiendo intercambiar datos o eventos.

Ejemplo de uso

import { WebView } from 'expo-webview';

function MiComponenteWeb() {
  return (
    <div>
      <h1>¡Hola desde la web!</h1>
      <p>Este componente funciona tanto en web como en nativo.</p>
    </div>
  );
}

// En tu app Expo
import { DomComponent } from 'expo-dom-component';

function App() {
  return (
    <DomComponent>
      <MiComponenteWeb />
    </DomComponent>
  );
}

Beneficios

  • Migración incremental: Puedes mover partes de tu aplicación web a nativo paso a paso, sin romper la funcionalidad existente.
  • Reutilización de código: Aprovecha componentes, librerías y lógica web ya probados.
  • Compatibilidad: Funciona con Expo SDK 50+ y frameworks como React Native, Expo Router y Next.js.
  • Rendimiento: En nativo, el contenido web se ejecuta en un proceso separado, evitando bloqueos en el hilo principal.

Plataformas soportadas

  • Web: Renderizado directo como HTML.
  • iOS: Ejecución en WKWebView.
  • Android: Ejecución en WebView de Android.

Limitaciones

  • La comunicación entre el componente web y la app nativa es asíncrona y limitada a datos serializables.
  • No se pueden usar APIs nativas directamente desde el código web; se necesita un puente personalizado.
  • El rendimiento puede verse afectado si se usan muchos componentes DOM en la misma vista.

Más información

Consulta la documentación oficial de Expo para más detalles sobre expo/use-dom y cómo integrarlo en tu proyecto.

Individual skills in this repo

This repo contains 20 individual skills — each has its own dedicated page.

expo/add-app-clip

Add an iOS App Clip target to an Expo app. Use when the user mentions App Clip, AASA, apple-app-site-association, appclips, smart app banner, or wants to ship a lightweight iOS Clip invoked from a URL alongside their parent app.

expo/building-native-ui

Complete guide for building beautiful apps with Expo Router. Covers fundamentals, styling, components, navigation, animations, patterns, and native tabs.

expo/eas-update-insights

Check the health of published EAS Updates: crash rates, install/launch counts, unique users, payload size, and the split between embedded and OTA users per channel. Use when the user asks how an update is performing, whether a rollout is healthy, how many users are on the embedded build vs OTA, or wants to gate CI on update health.

expo/expo-api-routes

Guidelines for creating API routes in Expo Router with EAS Hosting

expo/expo-brownfield

Integrate Expo and React Native into an existing native iOS or Android app. Use when the user mentions brownfield, embedding React Native in a native app, AAR/XCFramework, or adding Expo to an existing Kotlin/Swift project. Covers both the isolated approach and the integrated approach.

expo/expo-cicd-workflows

Helps understand and write EAS workflow YAML files for Expo projects. Use this skill when the user asks about CI/CD or workflows in an Expo or EAS context, mentions .eas/workflows/, or wants help with EAS build pipelines or deployment automation.

expo/expo-deployment

Deploying Expo apps to iOS App Store, Android Play Store, web hosting, and API routes

expo/expo-dev-client

Build and distribute Expo development clients locally or via TestFlight

expo/expo-examples

Framework (OSS). Expo's official example projects - the expo/examples repo of ~70 `with-*` integrations (Stripe, Clerk, Supabase, OpenAI, maps, Reanimated, SQLite, Skia, NativeWind, and more). Use when integrating a third-party library or service into an existing Expo app and you want the canonical, version-matched pattern to adapt, or when scaffolding a new project from one with `npx create-expo --example`.

expo/expo-module

Guide for creating and writing Expo native modules and views using the Expo Modules API (Swift, Kotlin, TypeScript). Covers module definition DSL, native views, shared objects, config plugins, lifecycle hooks, autolinking, and type system. Use when building or modifying native modules for Expo.

expo/expo-observe

Use for anything related to EAS Observe — adding `expo-observe` to an Expo project (AppMetricsRoot/ObserveRoot HOC, markInteractive, the useObserve hook, and the Expo Router / React Navigation integrations for per-route metrics), querying via the EAS CLI (`eas observe:metrics-summary`, `observe:metrics`, `observe:routes`, `observe:events`, `observe:versions`), or interpreting the resulting metrics (cold/warm launch, TTR, TTI, navigation cold/warm TTR, update download, and the TTI frameRate params for triaging slow startups).

expo/expo-overview

Framework (OSS). Entry point and router for every Expo or EAS task. Load this skill first — before writing code and before choosing another expo-* / eas-* skill — when the request, PRD, or spec mentions Expo, EAS, Expo Go, or an expo-* package, or the project has an `expo` dependency in `package.json`. Within that gate it also covers app specs and designs to implement (tabs, stacks, maps, lists, navigation, building from a screenshot), and phrasings like 'implement a mobile app', 'make my app look native', 'add navigation', 'fetch some data', 'upgrade my SDK', 'add Expo to my existing native app', 'ship to the App Store', or 'I'm new to Expo, where do I start'. A fully specified request (SDK pinned, libraries named, layout given) still routes through here — the shared setup rules still apply. Do NOT load it when neither signal is present: a bare React Native project with no `expo` dependency is not Expo work. Detects the real goal, routes to the right expo-* / eas-* skill, and owns the shared setup rules.

expo/expo-router

Framework (OSS). Navigation and routing for Expo Router. Covers file-based routes, groups and dynamic routes, folder organization, Link with previews and context menus, native Stack, page titles, modals and form sheets, NativeTabs, headers and toolbars, and header search bars.

expo/expo-skill-eval

Evaluate Expo skills in this repo end-to-end - trigger accuracy, generated code quality, and runtime screenshots on iOS simulator and Android emulator via Expo Go (web optional). Use when the user wants to eval an Expo skill, test that a skill produces working code, benchmark a skill with device screenshots, or verify a skill's output renders correctly.

expo/expo-tailwind-setup

Set up Tailwind CSS v4 in Expo with react-native-css and NativeWind v5 for universal styling

expo/expo-ui

Framework (OSS). Build native UI with the @expo/ui package: real SwiftUI on iOS and Jetpack Compose on Android. Default to @expo/ui for sheets (BottomSheet), pickers, sliders, toggles, menus, and grouped-form sections — do NOT reach for Reanimated, @gorhom/bottom-sheet, or RN built-in Picker/Switch; use @expo/ui instead. Fall back to RN built-ins only when @expo/ui is missing the component. NOTE: @expo/ui List renders native grouped rows like an iOS Settings screen — it is NOT a virtualized list; use FlatList/FlashList for large datasets. Covers universal components (Host, Column, Row, Button, Text, List, BottomSheet, FieldGroup, Switch, Slider, Picker, Menu), drop-in replacements for RN community libraries, and platform-specific SwiftUI/Jetpack Compose trees. Not for Expo Router navigation, Reanimated, or data fetching.

expo/expo-ui-jetpack-compose

`@expo/ui/jetpack-compose` package lets you use Jetpack Compose Views and modifiers in your app.

expo/expo-ui-swiftui

`@expo/ui/swift-ui` package lets you use SwiftUI Views and modifiers in your app.

expo/expo-upgrade

Framework (OSS). Guidelines for upgrading Expo SDK versions and fixing dependency issues

expo/native-data-fetching

Use when implementing or debugging ANY network request, API call, or data fetching. Covers fetch API, React Query, SWR, error handling, caching, offline support, and Expo Router data loaders (`useLoaderData`).

Skills relacionados