T3 Code Mobile

[!WARNING] T3 Code Mobile is currently in development and is not distributed yet. If you want to try it out, you can build it from source.

Quickstart

[!NOTE] Uses native modules so using Expo Go is not supported. You need to use the Expo Dev Client.

This app has three variants:

• development: Expo dev client, installable side-by-side as T3 Code Dev
• preview: persistent internal preview build, installable side-by-side as T3 Code Preview
• production: store/release build as T3 Code

Run commands from apps/mobile.

T3 Connect is optional and disabled in a fresh clone. Public configuration belongs in the repository-root .env or .env.local, not an apps/mobile/.env file. See ../../.env.example.

Development

For simulator/emulator development, select and boot a device, then ensure its native client matches this checkout before starting Metro:

The helper compares a local Expo fingerprint and the installed binary with its last successful build record. It builds and installs missing, stale, or unverified clients and reuses matching ones. Use check instead of ensure for a read-only decision: exit 0 means compatible, 2 means a build is needed, and 1 means an operational error. Run it on the simulator host; no EAS login is required. An externally installed client is unverified until the helper builds it once.

Start Metro for an already verified dev client:

Metro keeps its transform cache between ordinary starts. If the cache itself is causing stale or invalid output, clear it for one development-client start:

Run that reset once after installing or changing the Uniwind dependency patch. Cached transforms can otherwise reference its previous pnpm package path. Ordinary Metro starts still keep the cache.

Component edits use Fast Refresh. See mobile development lifecycle before changing runtime ownership or refresh behavior.

Build and run the local iOS dev client:

After changing a native dependency patch, rerun CocoaPods before rebuilding an existing iOS project. pnpm gives each patch hash a new package path; Pods can otherwise keep compiling the previous directory.

If your Xcode account only has a Personal Team, use a bundle identifier you control and opt into the reduced-capability local build. Personal Team builds omit the widget and share extensions, push entitlement, and native Sign in with Apple entitlement; builds without this opt-in are unchanged.

Build and install a self-contained Release app that does not need Metro:

The Personal Team equivalent also needs a unique bundle identifier:

Build and run the local iOS preview app:

Force the review diff highlighter engine:

javascript is the default and recommended setting for the review diff screen. Set EXPO_PUBLIC_REVIEW_HIGHLIGHTER_ENGINE=native only when you explicitly want to test the native Shiki engine.

Inspect the resolved Expo config for a variant:

Run static checks for mobile native code:

The native lint task runs SwiftLint for Swift plus ktlint and detekt for Kotlin. Missing native tools are reported as warnings and skipped locally. CI installs the default toolset from apps/mobile/Brewfile before running the native checks.

EAS Builds

Preview and production variants use Expo fingerprinting so OTA updates only reach binaries with matching native dependencies, config plugins, and patches. CI uses the preview:dev profile to reuse a compatible native build when possible.

The development variant uses appVersion to avoid recalculating the native fingerprint for each Metro launch manifest. MOBILE_VERSION_POLICY can override either default. If you distribute a custom Release build with the development identity and publish OTA updates to it, set MOBILE_VERSION_POLICY=fingerprint for both its build and updates. Changing the runtime policy requires a native rebuild for OTA matching; an existing dev client can still load local Metro bundles.

For preview or production EAS environments, set T3CODE_CLERK_PUBLISHABLE_KEY, T3CODE_CLERK_JWT_TEMPLATE, and T3CODE_RELAY_URL as EAS environment variables. Expo config maps the canonical values into the mobile build.

Create a PR preview dev-client build manually:

Create a cloud dev-client build:

Create a persistent preview build:

Android equivalents: