Files
app-flutter/README.md
T
mikkeli 50081d5417
CI / Analyze & Test (push) Successful in 12s
CI / Debug APK (push) Successful in 57s
Starter display: boundary v0 client, readout, mark button, CI
Connects to svc-gw over one WebSocket, heartbeats, treats timeout_ms of
silence as a dead link, and retries commands under the same id until acked.
Shows link state, signals with stale/null/missing told apart, the raw stream,
a mock banner on the surface, and a Mark button that stamps the recording.
Android: keeps the screen on and binds the process to the USB NCM network
when the gateway is on it. CI mirrors android-stuff's host-mode runner setup.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01DDwfd6Ki8UfG4hK6W5YpJz
2026-10-09 20:23:00 +09:00

29 lines
1001 B
Markdown

---
type: reference
---
# Flutter display client
Part of **Project Yukart**, making an old 2008 Mitsubishi Z27AG a bit smarter with modern technologies.
This file serves as the minimalist portal to other docs
## What this repo is about
The in-car display. Renders vehicle telemetry and a moving map, and runs on a
tablet connected to the Orin over USB or WiFi.
Flutter rather than native Android so the display unit stays swappable — the
display is deliberately a separate unit from the compute, and nothing here should
assume it will always be an Android tablet.
It is a bus subscriber like any other display: it talks to the message bus and to
[svc-gw](gitea:yukart/svc-gw), never to hardware.
```bash
flutter test
flutter run --dart-define=YUKART_GW=ws://<host>:7700/ # default: the car Orin, ws://192.168.55.1:7700/
```
- For implementation practice guidelines, refer to the [guidelines](docs/GUIDELINES.md);
- For implementation plans and history, refer to [them](docs/impl/);