SuperAPI AI Directory

expo-ui-jetpack-compose

Coding & development

View repository

Updated 10-16 01:28

About this skill

The instructions in this skill apply to SDK 55 only. For other SDK versions, refer to the Expo UI Jetpack Compose docs for that version for the most accurate information.

When to Use

  • You need to build Android-native UI in Expo using @expo/ui/jetpack-compose.
  • The task involves choosing Compose views or modifiers, embedding them in Host, or translating Jetpack Compose patterns into Expo UI code.
  • You are working specifically against Expo SDK 55 behavior for Jetpack Compose integration.

Installation

npx expo install @expo/ui

A native rebuild is required after installation (npx expo run:android).

Instructions

import { Host, Column, Button, Text } from "@expo/ui/jetpack-compose";
import { fillMaxWidth, paddingAll } from "@expo/ui/jetpack-compose/modifiers";

<Host matchContents>
  <Column verticalArrangement={{ spacedBy: 8 }} modifiers={[fillMaxWidth(), paddingAll(16)]}>
    <Text style={{ typography: "titleLarge" }}>Hello</Text>
    <Button onPress={() => alert("Pressed!")}>Press me</Button>
  </Column>
</Host>;

Key Components

  • LazyColumn — Use for a Compose-native list when the platform-specific design calls for it; do not replace React Native lists universally. Wrap in <Host style={{ flex: 1 }}>.
  • Icon — Use <Icon source={require('./icon.xml')} size={24} /> with Android XML vector drawables from Material Symbols.

Limitations

  • APIs target SDK 55; check that version’s actual Expo docs and installed package before editing. Android/iOS examples are platform-specific, not interchangeable or proof of real-device behavior. Existing framework and user requirements take precedence.
  • Native rebuilds install/execute dependencies and change the project; review the intended development target first. icon.xml and app code are application assets, not bundled files.
  • Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
  • Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.