How sanheiii/mageki works
Project Type & Purpose
• Mageki is a cross-platform mobile application built using Xamarin. Its purpose is to let a mobile device act as a control interface (via USB or LAN) for a device running the “ongeki-io” service.
• The repository shows a multi-project solution with dedicated code for Android, iOS, and UWP, alongside shared logic that contains UI definitions, drawing components, IO communication (TCP/UDP), and dependency interfaces.
Analyzing the File Structure
• At the top level, you see the solution file (Mageki.sln) and separate directories for each platform: Mageki.Android, Mageki.iOS, Mageki.UWP.
• There is a shared core project (Mageki) that houses shared resources such as:
• UI elements (Views, XAML pages, TouchTracking),
• Drawables (custom drawn components for the controller interface),
• IO components (TcpIO, UdpIO, StaticIO, etc.),
• Dependency service interfaces (ICloseApplication, INfcService).
• Each platform-specific project contains its own implementation of dependency services (e.g., NfcService and CloseApplication) and custom renderers to support native look and functionality.
• Configuration files (manifests, csproj files, AssemblyInfo) exist for handling platform-specific build and deployment details.
Key Architectural Insights from the README
• The README emphasizes the theme and connection with “ongeki-io” (external device connection via USB or LAN) while also hinting at user interactions (touch interfaces, custom drawing) and dependency inversion (with native implementations provided per platform).
• There is a clear separation between shared logic (business, control flow, IO, rendering commands) and platform-specific UI and service implementations.