Skip to content
supastack
Browse documentation
MobileExpo

For AI agents: fetch the complete documentation index at /llms.txt, the full documentation corpus at /llms-full.txt, the agent skill at /skill.md, or this page as Markdown at /docs/mobile/builds.md (or send Accept: text/markdown).

Build and device verification

Separate a successful Expo export from release readiness.

Ask about this guide
Open in

Setup and configuration

Before any step, read Before you start and Terminal basics. These instructions assume you opened the full supastack monorepo in VS Code; its root package.json marks the repository root. In pnpm commands, a workspace package is an app or shared-code folder; in the product, a workspace is a team's data container and security boundary. corepack pnpm --filter ... selects one package from the monorepo while commands run from its root. If you opened only a synced mobile or desktop folder, it does not contain the Web backend, Docker setup, or root scripts: run the backend from this monorepo or a reachable hosted server, and use the platform folder's own scripts. An environment variable is a named setting stored in a local .env file or your hosting dashboard; restart the relevant app after changing it, and keep server secrets out of NEXT_PUBLIC_ and EXPO_PUBLIC_ values.

1. Open apps/mobile/eas.json and apps/mobile/app.json in VS Code to review development, preview, and production settings.

2. Add the native development client from the repository root with corepack pnpm --filter @supastack/mobile exec expo install expo-dev-client. Run corepack pnpm --filter @supastack/mobile typecheck, then corepack pnpm --filter @supastack/mobile build for the local JavaScript export.

3. For native testing, sign in to your Expo account, change the terminal folder with cd apps/mobile, then run npx eas-cli@latest build --platform android --profile development. Use ios to request an EAS cloud iOS build from any operating system; a Mac with Xcode is needed to run the iOS Simulator or compile locally. Expected: the export verifies the JavaScript bundle and EAS produces an installable native development app. See Expo's development build guide for why Expo Go cannot add native libraries.

The mobile workspace build invokes its export script. This validates bundling for the configured targets; store signing, distribution configuration, and physical-device acceptance remain separate work.

corepack pnpm --filter @supastack/mobile typecheck
corepack pnpm --filter @supastack/mobile test
corepack pnpm --filter @supastack/mobile build

Commands to copy

Follow the comments to see which folder a command runs in. If two terminals are labeled, open two terminal windows and keep the first command running while you use the second.

# From the monorepo root, install the native development client once:
corepack pnpm --filter @supastack/mobile exec expo install expo-dev-client
corepack pnpm --filter @supastack/mobile typecheck
corepack pnpm --filter @supastack/mobile build

# EAS needs to run where apps/mobile/eas.json is located:
cd apps/mobile
npx eas-cli@latest build --platform android --profile development

Implementation workflow

Run shared contract tests after changing a package consumed by mobile. Review native safe areas, keyboard behavior, readable text sizing, and reduced motion on the devices you intend to support.

Keep native purchases behind the existing RevenueCat boundary. A successful bundle must not introduce Stripe Checkout into the mobile interface as a substitute for a verified native purchase integration.

Use an EAS development build on iOS or Android to validate react-native-purchases against configured sandbox products. Expo Go and the workspace export script do not validate store transactions.

Verification and troubleshooting

If the EAS build says expo-dev-client is missing, repeat its install command and confirm apps/mobile/package.json now lists it. Run EAS from apps/mobile so it finds eas.json. If EAS reports a missing project or signing setup, check your Expo account and project settings. Expo Go and a successful export still do not test StoreKit or Play Billing; use an EAS development build with sandbox products. A cloud iOS build can be started on Windows or Linux; only local iOS Simulator/build work needs a Mac with Xcode.

Record the device, build, API environment, and sign-in method used for acceptance. Verify deep-link return, session restoration, denied entitlements, and sign-out. Report export success separately from store and device verification.

When the export passes and a release is the goal, follow Submit to the app stores — the shipped eas.json profiles and build:/submit: scripts carry the app to Google Play and the App Store.

If you want to continue setup, read Store publishing.

Frequently asked questions

14 questions

What is supastack?

supastack is a modular foundation for building AI-powered SaaS products. It brings together common infrastructure so you can focus on product-specific features.

Does it support web and mobile?

Yes. supastack includes Next.js and Expo apps as starting points for web and mobile experiences.

What authentication is included?

Better Auth covers email OTP, magic-link, and social sign-in; email/password stays available at the API layer and through the Auth.js credentials engine for products that need it. Personal workspaces are provisioned with the account so product records stay scoped from day one.

How does it support AI?

supastack includes configurable multi-provider AI, usage tracking, budgets, and encrypted bring-your-own-key support.

How are subscriptions handled?

For products built on the kit, Stripe billing, subscriptions, and entitlements form the paid-access foundation. Provider secrets stay server-only.

Where does my product-specific code live?

Product-specific features remain in a separate codebase while the product configures and integrates supastack’s foundation modules.

How does supastack pricing work?

The kit is a one-time purchase with lifetime updates: One Platform at $249 (temporary launch price, $100 off the regular $349) — your pick of Next.js (Web), Expo (iOS & Android), or Tauri (macOS & Windows Desktop) — or the All Platforms Bundle at $499 (temporary launch price, $100 off the regular $599) with every platform and the full monorepo, plus $75 per extra developer seat. No kit subscription. Checkout on this site delivers your license key by email, with repository access via GitHub invite.

How do workspaces scope my data?

User-owned records are scoped by workspaceId. Identity, entitlements, AI usage, billing events, and audit entries stay inside the personal workspace boundary.

How do background jobs work?

Trigger.dev is the explicit job runtime. The JobRunner contract only promises enqueue, status, and cancel—workflow semantics stay Trigger.dev-specific and explicit.

How is email different from outreach?

Transactional email covers product workflows such as completion notices. Cold outreach and campaigns are product concerns outside this kit’s email module.

How do mobile purchases work?

Mobile includes native purchases and restore through RevenueCat, with access verified by your server. Configure the store accounts and complete device testing before release. Web billing remains separate.

Where do AI provider keys live?

Bring-your-own-key credentials are encrypted and stay server-only. Keys are redacted from logs; usage and budgets remain visible at the workspace level.

Which payment methods does checkout accept?

The Stripe-hosted checkout accepts cards and can also offer Alipay and WeChat Pay once those wallets are enabled on the Stripe account — handy for buyers in China. Wallet authorizations confirm asynchronously, so the license page updates as soon as the payment clears.

Can I get a refund?

After you've got access to the repository, supastack is yours forever, so it cannot be refunded. But rest assured, you get the complete source code with lifetime updates to build and ship unlimited products for yourself or clients. You just cannot resell the code or redistribute the repository as a starter kit or template.

EN
Theme