repowiseroutinemiku/apkstart

Architecture of routinemiku/apkstart

routinemiku/apkstart is 137 source files holding 1,165 symbols across 5 modules, written mainly in JavaScript, Python, Shell. The largest module is src, with 47 files, and 3 files are entry points into the dependency graph.

How apkstart fits together

The main process in src/main.js sets up the app, registers the inter-process messages that the windows send, and opens a window when a user launches an Android app. The UI entry point is src/ui/app.js. The core work happens in src/core, where the Runtime class owns the emulator, the provisioner and the ADB client, and the UI and scripts reach the emulator through it. src/core/emulator.js runs the Android emulator on Windows, and src/core/apk.js reads APK files before they are installed. The check-*.js scripts in tools exercise launch, quit and update behavior, and each one loads the core services it tests from src/core.

Largest modules

  • src: 47 files and 15,490 lines of code
  • test: 23 files and 4,500 lines of code
  • tools: 12 files and 793 lines of code
  • scripts: 4 files and 380 lines of code
  • docs: 2 files and 216 lines of code

Languages

By file count: JavaScript 86 files, Python 1 file, Shell 1 file.

Documentation

Repowise documents apkstart in 123 pages generated from the source, 9 of them written explanations of the repository and its modules. Module guides include:

  • scripts: Developer Scripts and Self-Tests
  • src/core: Device Backend Services
  • src: Electron Application Shell

More on apkstart: summary and FAQ, codebase overview, code health.

Related guide: Best dependency graph tools for monorepos