Mobile Build iOS and Android

Mobile: Build - iOS and Android

Native build configuration and the remote app-update policy. Part of Mobile Overview. Release conventions: Release Process.

iOS (ios/)

Podfile, mobileAppYC.xcworkspace (open the workspace, not the .xcodeproj), mobileAppYC.xcodeproj, link-assets-manifest.json. Version fields MARKETING_VERSION / CURRENT_PROJECT_VERSION in the pbxproj. First run:

# from apps/mobileAppYC
pnpm run start                 # Metro
pnpm run ios                   # build + launch simulator

Android (android/)

app/, build.gradle, settings.gradle, gradlew, gradle/. versionCode / versionName in android/app/build.gradle; release signing via my-release-key.keystore + YC_RELEASE_* gradle props.

pnpm run android

Shared native config

• Firebase: firebase.json (root). Native linking: react-native.config.js; assets via react-native-asset.
• Amplify outputs devamplify_outputs.json / prodamplify_outputs.json (gitignored, mocked in tests) select dev vs prod backends.

Remote app-update policy

src/features/appUpdate/services/appUpdatePolicy.ts drives the update gate:

• evaluateAppUpdatePrompt, compareVersions, getCurrentAppIdentity, shouldShowOptionalPrompt; types AppUpdatePrompt / UpdatePromptKind.
• Driven by remote MobileConfig.appUpdate, rendered by appUpdate/components/AppUpdateBottomSheet.tsx, and gated in App.tsx's AppUpdateGate (supports off / optional / required flows with store-URL deep links).

This is the client half of the Mobile App Update plan (the backend serves the policy via the mobile-config endpoint).

Release tags

Mobile ships as discrete tagged releases (mobile-vX.Y.Z-iOS-vA.B); app-store submission is a separate manual step. See Release Process.

Related

• Plans: Mobile App Update · Release Process · Mobile Overview · Mobile: Testing