mutyshwarzkopf-a11y/yggpeerchecker

Purpose and Entry Point

YggPeerChecker is a native Android utility for importing Yggdrasil peer/SNI host lists, resolving names, and measuring reachability and latency. The application starts in app/src/main/java/com/example/yggpeerchecker/ui/MainActivity.kt; Android packaging, permissions, and activity registration are defined in app/src/main/AndroidManifest.xml.

UI Shell and User Workflows

The UI is organized into three functional areas: checks, list management/viewing, and system settings/logs. app/src/main/java/com/example/yggpeerchecker/ui/checks/ChecksScreen.kt, app/src/main/java/com/example/yggpeerchecker/ui/lists/ListsScreen.kt, and app/src/main/java/com/example/yggpeerchecker/ui/system/SystemScreen.kt are the primary workflow boundaries. Theme selection is application-wide state managed by app/src/main/java/com/example/yggpeerchecker/ui/theme/ThemeManager.kt.

Check Orchestration

ChecksViewModel coordinates user-selected check type, filtering, sorting, concurrency, and displayed results. It consumes persisted hosts, executes probes, and groups output for presentation via app/src/main/java/com/example/yggpeerchecker/data/GroupedHost.kt and app/src/main/java/com/example/yggpeerchecker/ui/checks/GroupedHostCard.kt. Session-scoped UI/check state is represented by app/src/main/java/com/example/yggpeerchecker/data/SessionManager.kt.

Network-Probing Boundary

Probe implementations are isolated under utils, separating Android/UI concerns from network operations. app/src/main/java/com/example/yggpeerchecker/utils/ActiveProber.kt appears to be the central active-check dispatcher, while PingUtil.kt, YggConnectChecker.kt, SniChecker.kt, and TracertUtil.kt implement specific network measurements. Supported peer transport schemes include TCP, TLS, QUIC, WebSocket, and secure WebSocket; the bundled app/libs/yggpeers.aar is a material external Android library dependency likely used for Yggdrasil-peer functionality.

Host Ingestion, Parsing, and DNS

List management imports preset remote sources plus clipboard/file-provided content, then normalizes entries into host records. The parsing boundary is app/src/main/java/com/example/yggpeerchecker/utils/UrlParser.kt; host discovery/representation uses app/src/main/java/com/example/yggpeerchecker/data/DiscoveredPeer.kt. DNS resolution and fallback/“always check resolved IPs” behavior are handled by app/src/main/java/com/example/yggpeerchecker/utils/DnsResolver.kt and app/src/main/java/com/example/yggpeerchecker/utils/NetworkUtil.kt.

Persistence and Repository Layer

Room-style local persistence stores hosts, DNS cache entries, and historical check results. The database root is app/src/main/java/com/example/yggpeerchecker/data/database/AppDatabase.kt, with entities/DAOs such as Host.kt, DnsCache.kt, and CheckResult.kt. app/src/main/java/com/example/yggpeerchecker/data/repository/HostRepository.kt is the principal boundary between ViewModels and storage, enabling list filters, bulk DNS operations, clearing, and retrieval for checking.

Runtime, Infrastructure, and Observability

This is a Kotlin/Gradle Android application targeting Android SDK 34 and requiring JDK 17 for builds; module dependencies and packaging are in app/build.gradle. It relies on device network connectivity, external peer-list endpoints, DNS infrastructure, and target hosts rather than a server-side backend. Persistent application logging is centralized in app/src/main/java/com/example/yggpeerchecker/utils/PersistentLogger.kt and surfaced through app/src/main/java/com/example/yggpeerchecker/ui/system/LogsTab.kt.