Your existing desktop AionUI WebUI, on Android.
An unofficial prototype that opens your computer’s AionUI WebUI in Android WebView. Your computer still runs AionUI and its agents; keep it running and reachable. Chats, sign-in and uploads use the existing WebUI. This project is not affiliated with or endorsed by AionUI.
Release notes · SHA-256 checksum
Requires Android 8 or newer. The download is a debug-signed prototype APK for manual installation.
- Prepare your computer. Start your existing desktop AionUI and enable its WebUI so it is reachable from your phone. Use the upstream WebUI setup guide for your installed version. Use the WebUI attached to your existing desktop installation to access those conversations.
- Connect your devices. Put the phone and computer on the same trusted Wi-Fi, or use a Tailscale connection you have already configured. The computer’s WebUI must be reachable over that connection.
- Install on your phone. Tap Download APK v0.1.2 above, open the downloaded APK and follow Android’s installation prompts. If asked, allow your browser or file app to install this APK. No developer options or USB connection are needed for this route.
- Enter your computer’s address. Open AionUI Remote and enter the computer’s root HTTP(S) URL, including its port, in the server address field. Tap Connect. For HTTP, first select Allow HTTP for this server, then accept the Connect to this server? confirmation when prompted.
- Sign in through the WebUI. Follow the login screen on your phone. If it asks for a pairing code, get a fresh code from your computer’s WebUI settings, enter it on the phone, then approve the request in the desktop app. Follow the prompts for your installed AionUI version; its sign-in flow may differ.
Use the computer’s reachable WebUI address, not a chat-page link. Replace these fictional examples with your own address and port:
| Example | Illustrative root URL |
|---|---|
| HTTPS hostname | https://desktop.example.test:25808 |
| HTTP hostname | http://desktop.example.test:25808 |
| Documentation-only IP | http://192.0.2.10:25808 |
These examples will not connect to your computer. Enter only the root address: no chat path, query, fragment or embedded credentials. localhost on the phone refers to the phone, not your computer.
Important
HTTPS is recommended. HTTP is unencrypted and needs the explicit per-server choice and Connect confirmation. That choice does not prove VPN protection. Use HTTP only on a trusted LAN or a protected connection you already configured. The app does not configure or detect VPN protection, change firewalls or expose your computer’s WebUI.
Use AionUI’s existing WebUI to open conversations and chat. Its file controls can request Android’s system document picker; the app needs no broad storage permission. Successful upload and server receipt remain unverified for this release.
Tap the floating ⋮ options button for these native controls:
| Menu action | What it does |
|---|---|
| Change server | After confirmation, clears local sign-in cookies, site storage, cache and navigation, then returns to setup. The previous root is editable hint text only; it never reconnects automatically. HTTP consent must be chosen again. |
| Move options button | Choose Top left, Top right, Bottom right or Bottom left. The corner is remembered across app recreation and Reset/Change. |
| Reload page | Asks for confirmation before reloading. Unsent text may be lost. |
| Reset local session | After confirmation, clears local browser data and reopens the current server root. It does not revoke the desktop session. |
Reset and Change server can require signing in or pairing again on the phone. Handled rotation and window-size changes retain the live WebView. Actual Activity or process recreation rebuilds it from the saved safe URL/root; unsent draft recovery and background streaming are not guaranteed.
| Problem | Check |
|---|---|
| Computer cannot be reached | AionUI and its WebUI are running; the URL and port belong to the computer; your Wi-Fi or configured Tailscale connection can reach it. Try that same URL in the phone’s browser to narrow down the problem. |
| Pairing does not finish | Get a fresh code from the desktop’s WebUI settings and check the desktop app for its approval prompt. Follow the sign-in flow shown by your installed version. |
| Blank page | Check that your phone’s Android System WebView/Chrome provider is current and compatible. See whether the same URL loads in the phone’s browser. |
| HTTPS certificate error | Use an address with a valid, trusted certificate that matches its hostname. The app cancels certificate errors and offers no TLS bypass. |
Note
Source review, a successful build, the existing 6 unit tests and APK package installation have been verified. Formal checks for authenticated chat, uploads, session recovery and the remembered-corner/setup-hint UX remain incomplete. Implemented features and package installation do not establish that every phone flow works.
Supported external web links open in your browser. Pairing and sign-in remain managed by your desktop’s WebUI.
Build from source and optionally install with ADB
Navigation policy: Same-origin pages stay in WebView; supported external HTTP(S) destinations are offered to a browser. WebView navigation guards are not a universal pre-request firewall.
| Item | Version |
|---|---|
| JDK | 17 |
| Android SDK / Build Tools | Platform 36 / 36.0.0 |
| Gradle distribution | 8.14.5 |
| Android Gradle Plugin | 8.11.0 |
| Kotlin Android plugin | 2.2.20 |
| Minimum / compile / target SDK | 26 (Android 8) / 36 / 36 |
| App version / versionCode | 0.1.2 / 3 |
| Application ID | com.aionui.remoteprototype |
Set ANDROID_HOME to your installed Android SDK. On macOS/Linux:
./gradlew clean :app:assembleDebug :app:testDebugUnitTest :app:lint
mkdir -p release-assets
cp app/build/outputs/apk/debug/app-debug.apk release-assets/aionui-remote-prototype-0.1.2-debug.apk
shasum -a 256 release-assets/aionui-remote-prototype-0.1.2-debug.apk > release-assets/aionui-remote-prototype-0.1.2-debug.apk.sha256On Windows, use gradlew.bat with the same Gradle tasks. The wrapper downloads the configured Gradle distribution on first use; third-party notices identify the retained bootstrap JAR separately.
Local builds use your local Android debug signing key; keep its private key local. The public APK is debug-signed, not a production-signed or Play Store release. A locally built APK may have a different signer from the public download; do not assume it can update that installation.
Enable developer options and USB debugging on your phone, connect it to the computer and authorize ADB. Substitute its serial below:
"$ANDROID_HOME/platform-tools/adb" devices -l
"$ANDROID_HOME/platform-tools/adb" -s <serial> install -r release-assets/aionui-remote-prototype-0.1.2-debug.apk
"$ANDROID_HOME/platform-tools/adb" -s <serial> shell am start -n com.aionui.remoteprototype/com.aionui.remote.MainActivityFor a compatible update, install -r retains package data. Updating can restart the app process; unsent draft recovery is not promised. release-assets/ and build outputs are ignored by Git.
The app-owned source license is unspecified. Third-party notices and the accompanying license texts cover their listed components only; they do not grant an app-wide license or AionUI brand rights.