How eclipse-lmos/arc-view works
Project type and purpose
• This is a multiplatform Flutter UI client ("Arc View") for interacting with a remote Arc Agent service over GraphQL.
• It runs on Android, iOS, Linux, macOS, Windows and Web. It uses Riverpod for state management, GraphQL & HTTP clients for data, and OIDC for authentication.
File structure
• Top-level platform folders: android/, ios/, linux/, macos/, windows/, web/ → Flutter runtimes and platform embedder code.
• lib/ → contains the entire Dart application under src/, subdivided by feature (authentication, chat, conversation, events, metrics, usecases, tools, prompts, tests, settings, audio, core UI, client services, layout).
• assets/config/app-config.yaml → runtime configuration.
• Dockerfile, .devcontainer → containerized development.
• helm/arc-view-web-chart → Kubernetes Helm chart for deploying the web build.
• CI/CD workflows (.github/workflows) → build, publish, compliance.
README for additional insights
• The README confirms: Flutter app, communicates with ARC Agent GraphQL endpoint, uses Riverpod, supports code-generation (build_runner), and web optimized with wasm.
Elements
• Clear labels: e.g., “UI: Chat Screen”, “Provider: ChatNotifier”, “Service: MessageSender”, “External: Arc Agent GraphQL API”
• From UI → Providers → Services → External APIs
• Config Loader → Services
• Helm Ingress → Web Static Assets