Repository navigation
feat(mobile): Tauri Android/iOS companion with APK build and QA evidence - #13
Merged
Merged
Conversation
Indosaram
marked this pull request as ready for review
October 21, 2026 02:19
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Scope
Separate
mobile/Tauri v2 companion for Android and iOS, embedding RemoteApp locally. PTYs/daemon remain on desktop. No filesystem/terminal IPC commands or native plugins exposed. Native phone internals route to RemoteApp, not desktop App/IPC. Native service workers disabled; HTTPS/WSS-only CSP.Verified
npm run android:build -- --debug --target aarch64 --apkcommand afternpm run android:init.com.ferryx.mobile, version 0.1.0, min SDK24/target35, ARM64 native library present. Debug-signed, not a store release.Evidence:
docs/evidence/mobile-tauri-20261019/(build log, APK verification/hash, test summary, measured coverage, screenshots).Why still draft
mobile/README.mddocuments prerequisites, commands and remaining gaps. Android initialization pins available tooling and fixes the generated Node callback path. Generated SDK projects and APKs are not committed. No main push/merge or store deployment.