New app: desk dockt

Seth Hootsrequested to merge
sethhoots/fdroiddata:new-app-desk-dockt into master

Abstract

Please introduce the functions and usage of your app in summary, and also attach some screenshots.

desk dockt is a new MIT-licensed Android companion and Python desktop host. Move the mouse across the chosen desktop edge to control Android with keyboard, pointer, clicks and scrolling, then return through the phone edge. It supports USB/ADB and optional certificate-pinned TLS Wi-Fi, Unicode input, Android screenshots, opt-in text clipboard sharing, saved Connect on start and a one-time setup guide. Version 0.2.5 adds automatic clipboard resend on capture and a draggable monitor/phone layout with proportional corner overlap.

Source: https://github.com/uncannyowly/DeskDockt Release: https://github.com/uncannyowly/DeskDockt/tree/v0.2.5 Owner/author: uncannyowly; submitted at the owner's explicit request. Package: io.github.deskdockt.android The desktop host includes GNOME Wayland/InputCapture, Linux X11, Windows and macOS backends. Windows/macOS hardware validation remains pending.

Connection choice Home

Please elaborate why you wrote this app. Please highlight the unique functions it provides over other similar apps in F-Droid.

An abandoned input-sharing workflow depended on unavailable activation infrastructure. This project implements that workflow in new Android and Python source under MIT, without an account, activation server, ads, analytics or cloud relay. The original proprietary DeskDock APK, repair binaries and reverse-engineering work are excluded. This is a distinct app and package, not an update or relicensing of the old APK. It offers screen-edge input switching plus both ADB and authenticated local Wi-Fi; it is not PC video streaming. The app owner authorized inclusion; no consent from the old proprietary app's author is asserted.

Checklist

Policy

  • The app complies with the inclusion criteria.
  • The original app author has been notified (and does not oppose the inclusion). If you are not the author, please paste the link of the reply from the author.
  • The upstream app source code repo contains the app metadata in a Fastlane or Triple-T folder structure. The summary and description must be included and images, icon, and changelog should also be provided for better user experience. The en-US locale must be included.

Docs

Merge Request Setup

Metadata

  • Metadata must be put in metadata/<applicationId>.yml.
  • Metadata must be a valid YAML file.
  • Metadata must use LF as line ending.
  • Don't add summary/description/changelog/images or anything that should be provided in upstream repo. Please check the Changes tab to make sure there is no other unrelated files added in the MR.
  • Releases are tagged and auto update is enabled unless there is a special reason.
  • There is an issue tracker and contact info of the author so that we can report bugs and contact the author.
  • An AuthorName must be added. It doesn't need to be the real name.
  • External repos are added as git submodules instead of srclibs. You can update git submodules without opening an MR in this repo and the submodule is covered by our scanner.
  • Enable Reproducible Builds. We'll use your signature for improved security/reliability, also allowing users to switch between different channels. Do note that if you don't enable reproducible build then the apk will be signed with our key so you can't enable it later. If you can't enable this, please add the reasons here.
  • Setup abi split if the APK is large and the splitted ones can be much smaller.
  • Only the latest versions should be kept in the metadata before it's merged. If you update the metadata, please replace the old versions with the new ones.
  • Don't add any disabled versions in the metadata.
  • The commit field should be the full hash. Please don't use tag or branch in commit.

Pipeline

  • All pipelines should pass.
  • All warnings and errors in the Reports tab should be fixed or explained.
  • F-Droid CI runners are under GitLab's FOSS program, so there's no need for you to pay for any CI time. If Gitlab starts asking for phone numbers or credit cards don't submit anything, just leave a note in the MR so we know we need to trigger the CI.

Clarifications and validation

  • This corrects the template omission that caused this request to be closed. The source branch is updated to 0.2.5; only one app metadata file changes.
  • No JNI, runtime third-party Android libraries or executable downloads. The accessibility service injects gestures and does not retrieve window contents. Clipboard sharing is opt-in.
  • External repos/submodules and ABI splits are not applicable: the companion is a small pure-Java APK (~103 KB) without native code.
  • Reproducible upstream signatures are not configured yet. Upstream distributes its signed APK inside a ZIP because its website rejects raw APK uploads; a direct Binaries URL and reproducibility/signature verification need to be arranged. F-Droid may sign its build independently; upstream and F-Droid installs must not be presented as signature interchangeable.
  • JDK 17, Gradle 8.13, AGP 8.13.2, Android platform android-37.0 and build-tools 37.0.0. The exact source commit is pinned in metadata.
  • Local release/debug builds and lint pass. All 58 desktop checks pass on an isolated X11 display. A simulated edge transition into the Android 15 release emulator delivers clipboard text for Ctrl+V without manual Send.
  • The previous 0.2.4 F-Droid pipeline passed every job, including building the APK. The new 0.2.5 pipeline is still running; its status is not yet represented as a pass.
  • No other related inclusion/RFP issue is known. Existing submission: this MR.
Edited by Seth Hoots

Merge request reports