How ahmedgannoun/arcto works
Main Components
• Landing-Page (Next.js marketing site)
• Remote PWA (React/Vite Progressive Web App)
• Electron Controller (Desktop app – Node/Electron)
• Shared Utilities (common code if present)
Component Responsibilities
a. Landing-Page
– Serves marketing content, download links, and documentation via Next.js pages.
b. Remote PWA
– Runs in mobile browsers or installed as PWA; provides UI for navigation, media, volume, fullscreen, and power toggle.
– Communicates over WebSocket or HTTP to Electron Controller.
c. Electron Controller
– Runs on desktop; hosts a local server or WebSocket endpoint.
– Receives remote commands and triggers OS events or presentation APIs.
d. Shared Utilities (if “shared/” exists or later added)
– Houses shared TypeScript types, constants, and helper functions used by both PWA and Electron.
e. Public Assets
– Static images and manifest files for PWA and landing site.
Interactions and Data Flows
– Remote PWA → Electron Controller: WebSocket/HTTP for command messages (e.g., “next slide,” “play media”).
– Electron Controller → OS/Presentation App: Emulates keyboard or uses presentation API.
– Landing-Page → User’s Browser: Static site hosting via Next.js server or static export.
– Optionally: Telemetry or error reporting from Remote PWA back to a monitoring service if present.
Architectural Patterns
• Monorepo structure for code sharing and unified tooling (npm scripts, TypeScript config).
• Frontend–Backend separation: PWA as client, Electron as server.
• PWA pattern: service worker, manifest.json, offline support.
• Micro-apps under “apps/” directory.
• Next.js for SSR/SSG on Landing-Page.
• Vite for fast local dev on Remote PWA.
• Electron bridging Node.js backend with desktop capabilities.
– Clear component labels (include framework/tech under each).
– Group apps visually under a “Monorepo” boundary to emphasize shared repository.