Android companion app for a paired Androdex Desktop environment.
The current Android runtime is a paired WebView shell:
- pair Android with a desktop/server
/pairURL or QR code - store the paired origin and last opened route locally on the phone
- load the same desktop-served Androdex web app inside an Android-tuned WebView
This repo still contains the older bridge, relay, and native-client experiments, but those are now legacy/reference paths rather than the main end-to-end Android flow.
Current End-to-End Flow
- Start Androdex Desktop or the headless server on your computer.
- Generate a pairing link from the desktop app's Connections settings or from the server's headless startup output.
- Open the Android app and scan the QR code or paste the pairing URL.
- Android validates the pairing link, saves the paired origin, and opens the paired web app in-app.
Current UI
Desktop pairing page:
Android paired thread:
Android sidebar:
Build The Android App
cd android ./gradlew assembleDebug
The debug APK is written to:
android/app/build/outputs/apk/debug/app-debug.apk
Current app build facts:
- package name:
io.androdex.android - version:
0.2.2 - version code:
14
Project Layout
android/: current Android app sourceDocs/android-mirror-shell-architecture.md: current Android runtime architectureDocs/play-store/: Play Store notes, review guidance, and policy draftsandrodex-bridge/: legacy/compatibility macOS bridge package kept in-treerelay/: legacy/compatibility relay service kept in-treedesktop/: older control-room prototype inside this repo, not the canonical desktop repo
Legacy Components
The repo still includes the previous bridge-first architecture:
androdex-bridge/README.md: bridge CLI/service docsandrodex-bridge/src/README.md: bridge source guideDocs/android-sync-convergence.mdDocs/android-compose-structure.mdDocs/android-mac-native-test-matrix.md
Those documents are retained for reference, but they do not describe the shipped Android runtime entry anymore.
