Android and iOS
The mobile app is the same interface as desktop and web, built with Expo. It connects to your daemons; agents keep running on the daemon when the phone sleeps.
Android
Section titled “Android”| Download | frogg-<version>-android-arm64-v8a-unsigned.apk from GitHub releases |
| Devices | arm64 phones and tablets, Android 10 (API 29) or later |
| Store | Not on Google Play or F-Droid |
Install it by opening the APK on the phone and allowing installs from your browser or file manager.
Connect
Section titled “Connect”- Scan QR code: run
frogg auth pairon the daemon host and scan the code. - Paste pairing link: open or paste the
https://pair.frogg.app/code/...link. - Direct connection: enter the daemon’s LAN, VPN or Tailscale address and port.
A phone off your home network needs a route to the daemon: a VPN such as Tailscale, or a relay you operate. frogg does not provide a public relay. See connect and pair.
Voice and notifications
Section titled “Voice and notifications”- Dictation, voice alerts and Companion work on Android. Companion offers Call and Media audio modes; Companion on physical devices is still in preview.
- Push notifications need a build with Firebase configuration. Whether the published APK receives them has not been verified for these docs.
There is no iOS release. The app builds for iOS from source (npm run ios --workspace=@frogg/app
on a Mac with Xcode), and branding CI builds an unsigned simulator app, but no App Store or
TestFlight distribution exists.
Build from source
Section titled “Build from source”npm cinpm run android:development --workspace=@frogg/app # debug build on a connected devicenode scripts/release/build-android-apk.mjs --abi arm64-v8a --out-dir release-assetsRequires JDK 21 and the Android SDK. See development setup.