# Shipker Full LLM Context

Shipker is a mobile deployment automation product hosted at `shipker.dev`.

## Product Promise

Shipker helps mobile teams connect a GitHub repository, apply release automation, generate signing material for new apps, and ship to App Store and Google Play faster.

## Primary Workflow

1. Customer installs the Shipker GitHub App.
2. GitHub is the only login/signup provider.
3. Customer selects the repositories Shipker can access.
4. Shipker receives the installation id at `/github/setup`.
5. Dashboard shows app stats, release-readiness stats, and integration progress.
6. Channels lets the user complete the three required integrations: Shipker GitHub App, Google Play Console, and App Store Connect. The app uses those three connections to calculate internal readiness progress.
7. Settings shows GitHub session, backend state, and runner policy.
8. Shipker detects the mobile stack.
9. Shipker applies the deployment template from `C:\Intel\template`.
10. Shipker generates new-app signing material for iOS and Android.
11. Shipker asks only for app metadata, release track, and compliance details that cannot be inferred safely.
12. Shipker writes GitHub Actions secrets and variables.
13. Shipker opens a setup pull request.
14. Shipker runs dry builds before enabling store uploads.

## Supported Stacks

- Flutter
- React Native
- Native iOS with Swift or SwiftUI
- Native Android with Kotlin or Jetpack Compose

## Repository Access

Shipker uses GitHub App installation tokens for normal repository access. Customers do not need to provide a GitHub PAT for the app repository.

Shipker supports both personal/free GitHub accounts and organization/paid GitHub accounts. For an app repository named `tymasheen`, Shipker should create a private `ios-signing-tymasheen` repository under the selected GitHub owner. The current Fastlane template includes match signing storage; Shipker should replace customer PAT usage for signing repositories with a GitHub App installation token or a dedicated deploy key.

The first beta focuses on new apps. Shipker should not ask users to upload signing files for this path. For iOS, Shipker creates the signing repo, Apple distribution certificate, and provisioning profile. For Android, Shipker generates and stores the Google Play upload key. Existing app migrations should be handled later in a separate flow.

## Runner Strategy

- GitHub Actions macOS: default iOS runner.
- Azure macOS: secondary cloud runner.
- Local `macc`: controlled fallback for iOS signing/debugging only.
- Android: Linux-hosted runner by default.

## Domains

- `https://shipker.dev/`: product app and developer portal.
- `https://github.com/apps/shipker`: GitHub App install surface.
- `https://shipker.com/`: marketing website.