Skip to content

WI-H02: Enrol in the Apple Developer Program

WI-H02: Enrol in the Apple Developer Program

Problem

iOS device builds, TestFlight, and App Store submission all require an Apple Developer Program membership at $99/year. It is the only compulsory recurring spend in the project (docs/architecture.md §5).

It also becomes non-optional the moment Google sign-in ships on iOS: App Store Guideline 4.8 requires Sign in with Apple wherever third-party social sign-in is offered.

In scope

  • Enrol in the Apple Developer Program.
  • Record the Team ID where the mobile build needs it.
  • Register the app’s Bundle ID.
  • Enable the Sign in with Apple capability.

Out of scope

  • Google OAuth client IDs and Android fingerprints — part of WI-050.
  • App Store listing, screenshots, review submission.
  • Any Expo or EAS configuration.

Definition of done

  • Membership active; renewal date recorded on the issue.
  • Team ID recorded somewhere the mobile build can reach it (not committed — see security-and-secrets.md).
  • Bundle ID registered and matching apps/mobile configuration.
  • Sign in with Apple capability enabled.

Verification

Apple’s developer portal shows an active membership, and the Bundle ID appears under Identifiers.

Notes

Defer this until you actually need a device build or a store submission. There is no reason to start a yearly billing clock early — nothing in M0 through M3 needs it, and Expo Go plus email/password auth covers development until social sign-in arrives.

The trigger to stop deferring is WI-050. Per AGENTS.md, adding Google sign-in on iOS makes Sign in with Apple mandatory, which makes this membership mandatory in the same breath.