goon/mobile
jtrzupek 967123d5d6 mobile: let players identify & report 404/410 sources
When a host returns 404/410 at playback time (CDN gone, video removed) the
player previously showed only a raw error and a Back button — the user could
not tell it was a dead source or report it without going back to the detail
screen (bug a78cc3b6: "fpo i sxyprn to 404, którego apka nie potrafi
zidentyfikować").

- Thread playback_source.id into Player route params (scenes + movies).
- Native player error overlay: detect 404/410 in the ExoPlayer error, show
  "Source no longer available" and a "Mark broken" button that marks the
  source dead and returns. 403 is excluded (proxy/WebView fallback may save it).
- WebView player: add onHttpError; on a main-document 404/410 show the same
  overlay (Mark broken / Try anyway / Back) instead of the host's 404 page.
  Guarded to the loaded document (host+path) so same-host ad/subresource 404s
  don't false-trigger.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-06-01 11:04:58 +02:00
..
android fix(apk 0.2.1): in-app installer "nic się nie dzieje" + oo launcher icon 2026-05-31 13:15:37 +02:00
assets feat(brand): oo logo — app icons, landing, in-app mark (Gemini-generated) 2026-05-30 22:38:52 +02:00
src mobile: let players identify & report 404/410 sources 2026-06-01 11:04:58 +02:00
.gitignore Initial commit 2026-05-20 10:10:22 +02:00
app.json fix(apk 0.2.1): in-app installer "nic się nie dzieje" + oo launcher icon 2026-05-31 13:15:37 +02:00
App.tsx build(apk): 0.2.0 — expo-font native, runtime 1.1, fonts re-enabled 2026-05-31 12:51:32 +02:00
babel.config.js Initial commit 2026-05-20 10:10:22 +02:00
package-lock.json feat(mobile): custom fonts (General Sans + Geist Mono) + logo rework 2026-05-30 22:25:26 +02:00
package.json feat(mobile): custom fonts (General Sans + Geist Mono) + logo rework 2026-05-30 22:25:26 +02:00
README.md Initial commit 2026-05-20 10:10:22 +02:00
tsconfig.json Initial commit 2026-05-20 10:10:22 +02:00

goon mobile (Expo / React Native)

Mobile client do self-hosted goon backendu. iOS/Android jeden codebase.

Setup

cd mobile
npm install
npx expo start

Następnie:

  • Expo Go (iOS/Android): zeskanuj QR z terminala
  • Android emulator: npm run android
  • iOS simulator: npm run ios (tylko macOS)
  • Web preview: npm run web

Konfiguracja

Po pierwszym uruchomieniu zobaczysz ekran logowania:

  • Backend URL — adres twojego goon backendu, np.:
    • http://192.168.1.10:8000 (LAN)
    • https://goon.tvojadomena.dev (przez Cloudflare Tunnel/Caddy)
    • http://100.x.x.x:8000 (przez Tailscale)
  • API Key — klucz wygenerowany dla backendu, ustawiony w .env:
    API_KEYS=<klucz>
    
    Generowanie:
    python -c "import secrets; print(secrets.token_urlsafe(32))"
    

Klucz jest trzymany w expo-secure-store (Keychain na iOS, Keystore na Androidzie).

Ekrany

  • Login — backend URL + API key, weryfikacja przez /healthz + /scenes
  • Scenes — lista scen z search; pull-to-refresh
  • Scene detail — performerzy, tagi, źródła, opis
  • Merge queue — pending merge candidates, sortowane po score (desc)
  • Merge detail — side-by-side dwóch scen + reasons + akcje:
    • Merge → keep LEFT (default — left to wcześniejsza/kanoniczna)
    • Merge → keep RIGHT (gdy nowsza wersja ma lepsze metadane)
    • Reject (keep both) — to nie jest duplikat, zostawiamy oddzielnie

Stack

  • Expo SDK 52 + React Native 0.76 (new architecture)
  • TypeScript strict
  • React Navigation 7 (native stack)
  • TanStack Query 5 (cache, optimistic invalidation)
  • expo-secure-store (credentials)

Build .apk (sideload na Androida)

npx eas build --profile preview --platform android

Wymaga konta Expo. Bez niego można użyć expo prebuild + gradlew assembleRelease.

Dlaczego nie PWA

Wybrany RN+Expo zamiast PWA bo:

  • swipe gestures pasują do triage merge queue
  • secure-store jest natywny (Keychain/Keystore) zamiast localStorage
  • pull-to-refresh i FlatList virtualization out-of-the-box
  • Jeden .apk można rozdać testerom bez App Store