Android build — signed APK from `apps/client` with runtime-configurable API URL #187

New issue

Closed

opened 2026-06-20 15:44:54 +00:00 by james · 0 comments

james commented

2026-06-20 15:44:54 +00:00

Owner

Produce a signed Android APK / AAB from apps/client that points at a self-hoster's URL configured at runtime (no baked-in URL).

Scope

Decide between EAS Build (Expo's cloud) and self-hosted build runners — recommend self-hosted on a Forgejo Action runner for the self-hoster-friendly story.
Runtime URL: a settings screen captures the API base URL and persists in secure storage; default unset, no baked-in URL.
Sign with a project-managed keystore; document key rotation in an ADR-0014 follow-up if needed.
Tag-driven release: pushing vX.Y.Z builds an APK and attaches it to the Forgejo release (per ADR-0014 spirit).

Acceptance criteria

pnpm -F client build:android produces a signed APK on a fresh checkout.
The APK installs on Android 13+, prompts for a server URL on first launch, and exercises the full feature set.
Tag-driven release publishes the APK to the Forgejo release.
Release pipeline retains the existing signing + provenance guarantees for the API container image.

Out of scope

Play Store distribution.
iOS — not in idea.md.

Composes with

Release pipeline (ADR-0014), Linux Flatpak build, Expo client scaffolding.

Part of

#176

Produce a signed Android APK / AAB from `apps/client` that points at a self-hoster's URL configured at runtime (no baked-in URL). ## Scope - Decide between EAS Build (Expo's cloud) and self-hosted build runners — **recommend self-hosted on a Forgejo Action runner** for the self-hoster-friendly story. - Runtime URL: a settings screen captures the API base URL and persists in secure storage; default unset, no baked-in URL. - Sign with a project-managed keystore; document key rotation in an ADR-0014 follow-up if needed. - Tag-driven release: pushing `vX.Y.Z` builds an APK and attaches it to the Forgejo release (per ADR-0014 spirit). ## Acceptance criteria - [ ] `pnpm -F client build:android` produces a signed APK on a fresh checkout. - [ ] The APK installs on Android 13+, prompts for a server URL on first launch, and exercises the full feature set. - [ ] Tag-driven release publishes the APK to the Forgejo release. - [ ] Release pipeline retains the existing signing + provenance guarantees for the API container image. ## Out of scope - Play Store distribution. - iOS — not in `idea.md`. ## Composes with Release pipeline (ADR-0014), Linux Flatpak build, Expo client scaffolding. ## Part of #176

james added the

area:ci

area:native

feature

labels

2026-06-20 15:45:27 +00:00

james referenced this issue from a commit

2026-06-21 05:46:00 +00:00

feat(client): theme + i18n + auth glue + Notes reference + CI gates (#183)

james referenced this issue

2026-06-21 05:46:51 +00:00

feat(client): scaffold @carol/client — Expo Router + RN Web (#183) #198