expo-module

Topics in the source

• Writing Expo Modules
• When to Use
• References
• Quick Start
• Recommended Workflow
• Practical Scaffolding Rules
• Core File Shapes
• Module Structure Reference

Complete reference for building native modules and views using the Expo Modules API. Covers Swift (iOS), Kotlin (Android), and TypeScript. Creating a new Expo native module or native view Adding native functionality (camera, sensors, system APIs) to an Expo app Wrapping platform SDKs for React Native consumption Building config plugins that modify native project files Adding Android, Apple, or web support to an existing Expo module Editing expo-module.config.json, config plugins, or lifecycle hooks To migrate an existing Swift module from the definition DSL to the Expo Modules API 2.0 macros (@ExpoModule, @JS, @Event), use the expo-migrate-module skill (from the expo-experiments plugin) instead. Consult these resources as needed: Prefer create-expo-module over manually creating native module files and directories. In practice, the best path is usually to create the scaffold first and then build on top of it. The scaffold sets up the expected layout, expo-module.config.json, podspec or Gradle files, TypeScript bindings, and the standalone example app flow. If an existing Expo module only needs another platform, use create-expo-module add-platform-support instead of manually copying

This is an excerpt. Refer to the complete source and its current requirements.