wtclaude
3edd45d5f4
`brand.logo` and `brand.hero` have ridden in `BrandDto` since M1 and neither has ever been drawn — the app spells the instance out in text everywhere the website shows a mark. Phase 4 renders them on the three surfaces §5.6 names: the logo above the name in the drawer header, the logo in place of the uppercased title in the top bar, and the hero as a band above Home's title block. Nothing new is fetched. `LocalAssetResolver` already turns a site-relative `/uploads/…` path into an absolute URL and Coil is already a dependency, so this phase is entirely presentation. The rule that governs the file is §5.6's: an empty slot renders nothing — not a placeholder, not a reserved gap. Every size modifier hangs off the image itself, so when the image is not composed neither is its padding, and a caller that wants space below a hero passes `Modifier.padding` instead of a sibling `Spacer`. A failed load is an empty slot: no broken-image icon, no retry. The top bar is the one place where "empty" is not "nothing". The logo replaces the title there, so a 404 would strand the app in an unnamed shell until the next resume refresh; it falls back to the text, which is what empty already showed. There is no fallback while the load is in flight — drawing the text first would flash text to logo on every navigation for one frame. The hero is a fixed 180dp band, cropped, rather than the intrinsic aspect the app's other images draw at. The website's hero is a CSS background driven by `hero_layout`, which the app does not port, and the website's default hero is a square emblem — at the intrinsic aspect an uploaded square would be a ~360dp block that pushes the status card off the first screenful. It clips to `shapes.medium`, so it follows `--radius-card` like every other surface. The logo carries a content description only in the top bar, where it stands alone; beside the name in text it is decorative, the same call the website's `alt=''` makes. 410 unit tests green (401 + 9), `lintDebug` and `assembleDebug` clean. The drawing itself is out of reach for JVM tests — the app carries no Robolectric, so a composable body cannot run — but the decision of *whether* to draw is pure, and `brandAssetUrl` is pulled out so it can be pinned. Co-Authored-By: Claude <noreply@anthropic.com>
Runic Gateway — Android app
A native Android client for a Runic Gateway shard's public site + player self-service. It is
purely an API client of the website backend — it never talks to the link/ sidecar or the game
shard directly, and it ships none of the shard/sidecar wiring. It surfaces the same content and
player features as the website's browser client, minus every administrative/management console.
The authoritative design contract is docs/android/PLAN.md
in the RunicGateway/docs repo. The authoritative API reference is the committed OpenAPI spec at
website/server/swagger/swagger-output.json.
Status
M0 — repo scaffold. Gradle + Compose + Hilt skeleton with CI (lint + unit test + debug build). The functional Kotlin pass (M1–M4) and the design pass (M5) follow — see the plan's milestones (§9).
Stack
| Concern | Choice |
|---|---|
| Language / UI | Kotlin + Jetpack Compose (Material 3) |
| Navigation | Navigation-Compose, single-activity |
| HTTP | Retrofit + OkHttp, kotlinx.serialization |
| Async | Coroutines + Flow |
| DI | Hilt |
| Prefs / base URL | Jetpack DataStore |
| Tokens at rest | EncryptedSharedPreferences |
| Images | Coil |
| Min SDK | Android 10 (API 29) |
| Target / compile SDK | 35 |
Dependency and plugin versions are pinned in gradle/libs.versions.toml.
Build
Requires JDK 17 and the Android SDK (ANDROID_HOME / local.properties).
./gradlew assembleDebug # build a debug APK -> app/build/outputs/apk/debug/
./gradlew test # JVM unit tests
./gradlew lint # Android lint
./gradlew installDebug # install on a connected device/emulator
The app self-configures its server URL on first run (PLAN.md §3), so a single build works against any shard's website — there is no compiled-in API host.
CI
.gitea/workflows/pr-checks.yml gates PRs into main with ./gradlew lint test assembleDebug on the
org's self-hosted runner (JDK 17 + Android SDK). Debug builds are auto-signed, so the gate needs no
secrets. This pipeline is verified green end-to-end on the runner (M0). A signed release APK
attached to a Gitea release comes at M6.
The workflow carries a few runner-specific accommodations (each explained in comments in the file), because this self-hosted runner differs from a stock GitHub runner:
- JDK 17 is installed via
apt(notactions/setup-java) — the runner can't resolveapi.adoptium.net, while the Ubuntu mirrors are reachable. - SDK packages are installed explicitly via
sdkmanager, withset +o pipefailsoyesdying ofSIGPIPEdoesn't fail the step. gradlewischmod +x'd in the run step — the runner's checkout does not preserve the git executable bit, so./gradlewalone fails with "Permission denied".
Contributing
See CONTRIBUTING.md. AI-assisted contributions must be disclosed (org
policy): tick the PR box naming the tool and add a Co-Authored-By trailer to AI-authored commits.
Licensed GPL-3.0-or-later.