Deployment

Objective

• Get the Attik mobile app deployed so users can install and use it on their phones and tablets.
• Prefer distribution through the Apple App Store and Google Play Store so users can discover and update the app through normal store flows.
• Use TestFlight (and an Android equivalent if applicable) as a fallback so internal or beta users can access the app while store listings are pending or under review.

Background

• The mobile app is in development with the goal of letting inspectors use Attik on their devices without relying on the browser (per internal notes).
• Users need a reliable way to install and run the app on their devices.
• Store submission and review can take time; TestFlight (and similar) provide a path to early access and validation before public store release.

Scope

• Mobile (attik-mobile)
  The app lives in the workspace under attik-mobile (app root: attik-mobile/attik-mobile). It is an Expo app (Expo ~54, expo-router); entry and scripts are in package.json (expo start, expo start --ios, expo start --android). App identity and native config are in app.config.js: name "Attik Mobile", slug "attik-mobile", URL scheme "attikmobile", plus iOS and Android blocks (icons, Google Maps via EXPO_PUBLIC_GOOGLE_MAPS_API_KEY). There is no eas.json in the repo, so EAS Build and EAS Submit are not yet configured; adding them is in scope for store builds and TestFlight. The app reads backend URL and API key from constants/config.ts (env: EXPO_PUBLIC_API_URL, EXPO_PUBLIC_API_KEY); production or staged builds will need the correct API base URL. No CI workflows were found under .github; defining a build/deploy pipeline (e.g. EAS Build + optional submit) is in scope. Decisions needed: store accounts, signing and provisioning, and whether to use EAS Submit for TestFlight/Play internal testing.
• Backend / Frontend (attik-backend, attik-frontend)
  No mobile-specific deployment config exists in these repos. The mobile app already targets the existing backend (API key auth, EXPO_PUBLIC_API_URL). If the deployed app must hit a specific environment (e.g. production API base URL), that is configuration in the mobile app’s build/env (e.g. EAS environment variables); the backend does not need deploy changes for this. Deep links or universal links for the mobile app, if any, would use the scheme/config in attik-mobile/app.config.js; no frontend changes required for this task.

References

• Apple App Store distribution
• Google Play Console
• TestFlight for iOS
• Google Play internal testing / closed testing (Android beta options)
• EAS Build and EAS Submit (Expo Application Services for builds and store submission)
• Mobile app config: attik-mobile/app.config.js; env/API: attik-mobile/constants/config.ts; README: attik-mobile/README.md