0.2.2 + 0.3.0: remote threading fix, phone-first onboarding, ten-foot settings, self-healing errors, in-app updater, group filter
Some checks failed
Build TV app / build (push) Failing after 2s
Some checks failed
Build TV app / build (push) Failing after 2s
Squashed history rewrite: earlier revisions of the docs carried private hostnames; placeholders throughout history now. - Fix phone remote threading (welcome/get_state/broadcast) — remote connects and mirrors channels, Now/Next, favorites - Phone-first onboarding (ADR-0007): one QR, server URL + IdP login on the phone (closes #11) - Ten-foot settings + Erweitert sub-screen (closes #14), TvTextField D-pad focus fix (closes #9) - EPG grid envelope parsing, Now/Next live (closes #10) - Self-healing error states (closes #13), in-app updater (closes #12) - Channel group filter chips fed by Dispatcharr groups Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This commit is contained in:
13
docs/adr/0007-onboarding-via-remote.md
Normal file
13
docs/adr/0007-onboarding-via-remote.md
Normal file
@@ -0,0 +1,13 @@
|
||||
---
|
||||
status: accepted
|
||||
---
|
||||
|
||||
# Onboarding runs on the phone through the TV's own pairing server
|
||||
|
||||
Nobody should ever type on a TV. Instead of baking a server URL into the APK
|
||||
(rejected: publishes private infrastructure in a public artifact) or on-TV
|
||||
text entry (rejected: D-pad typing), first-run setup reuses the embedded
|
||||
remote-control server: the TV shows one QR, the phone opens the TV-served web
|
||||
app, and server URL plus IdP login (device-flow link opened directly on the
|
||||
phone) happen there. Requires phone and TV on the same LAN — acceptable, since
|
||||
the remote control has the same requirement by design.
|
||||
Reference in New Issue
Block a user