New app: OpenJump

New app: OpenJump

Offline Android video analysis for jumps and athletic performance. Six jump protocols, local athlete/history storage, user-triggered export/manual backup and experimental video-based velocity tracking. Not clinically validated.

  • Application ID: com.openjump.app.
  • Version: 1.0 / versionCode 7; minSdk 26, targetSdk 36.
  • License: GPL-3.0-or-later.
  • Source: https://github.com/cortig00/OpenJump
  • Issue tracker: https://github.com/cortig00/OpenJump/issues
  • Contact: openjump.app@gmail.com; upstream maintainer: cortig00.
  • Original Play-source tag: v1.0, commit 5c47e887dc06b294f9b9a1f6458df6b670f854aa.
  • Build source: 8cd1fea192bdd5e984e5bd5a74f8f6463129912f, publicly reachable on fdroid/inclusion; full hash pinned in the recipe. This later source adds licenses, Fastlane metadata and an original generic coffee pictogram. Same app logic, build configuration and code7; the Play release is not replaced.
  • Eight upstream Fastlane locales: en-US, es-ES, de-DE, fr-FR, it-IT, pt-BR, pt-PT, tr-TR. Default icon; two protocol screenshots each for EN/ES/DE/FR, other locales use default graphics. No real athlete records/video frames.
  • No Anti-Features proposed. No Play Services/Firebase/proprietary SDK/ML model, ads or analytics/backend. INTERNET is removed from the merged manifest. Optional source/donation/DOI/browser links and user-initiated sharing are not required for the offline features. Maintainers decide the final labeling.
  • Runtime/build dependency licenses, assets and native sources audited: notices, assets, validation.
  • Regular stable-tag auto-updates enabled; version extraction from version.properties. Initial build intentionally uses the later preparation commit instead of moving the immutable original Play tag.

Signing / reproducibility exception

Please use normal F-Droid signing. The maintainer explicitly accepts a different certificate for the same application ID. Switching Play/F-Droid requires manual backup, uninstall and restore; installations cannot update across certificates. No Play upload/App Signing key is supplied or requested.

The already-published Play artifact remains immutable. This first F-Droid source adds license assets and replaces a donation-service logo with original artwork; it is not claimed to match that signed Play artifact. Two local builds of the pinned source were byte-identical, but both ran in the same container with cache reuse, not independent clean-room/Play-signature reproducibility. Binaries and AllowedAPKSigningKeys are deliberately absent. We are not deferring a required signature check or claiming that changing the signing certificate later is free of migration consequences.

ABI split exception

The unsigned universal APK is 12,800,626 bytes. All four ABIs' native libraries together are just 202,140 compressed bytes. Splitting would save less than 0.2 MiB per APK, so no ABI/version-code recipe complexity is introduced.

Local validation (not GitLab CI)

Official fdroidserver:buildserver container; fdroidserver source revision c21c177ff6d813697aaf9c988ca9fbb2b571b468; OpenJDK21, platform36, build-tools35.0.0, AGP8.9.2, Gradle8.11.1. No host signing configuration/keys.

  • fdroid rewritemeta, fdroid lint: PASS with official categories.
  • Source scanner: zero warnings/errors; default wrapper cleanup only.
  • Real fdroid build --scan-binary: PASS from the exact public source hash; binary class/signing-block scanner PASS, no scan suppression.
  • fdroid checkupdates: PASS, finds 1.0 / code7 via v1.0.
  • Repeated local build: same APK SHA-256 7b6954b1be5da52114e896023e745f7e773e0c49d9044610476e3c946c78ef30.
  • All 13 DEX/native entries equal the original-source Linux baseline build; license assets present. APK intentionally unsigned.
  • Real fdroidserver text/image importer: eight locales and expected graphics PASS.
  • App debug and AndroidTest packaging, debug/release lint and diff checks PASS. JVM/test source tasks are NO-SOURCE in this minimal public distribution; no instrumented suite or independent accuracy qualification is claimed.
  • Focal debug AVD smoke: launch, About 1.0(7), generic donation icon and offline GPL screen; no app FATAL/ANR. No personal device touched.

Upstream release state

Keep v1.0 immutable at the original Play source. A draft GitHub Release OpenJump 1.0 (7) has been prepared with no attached binaries or signing material; it is not a published release. The maintainer can review/publish it separately from F-Droid approval; it must not advertise an accepted F-Droid download yet. The preparation branch remains separate from main. Before future releases, integrate its files without orphaning the pinned source commit (prefer fast-forward or a merge retaining history; do not discard/squash and delete its only reachable branch while the first recipe pins that commit). Future versions must increase code and tag the exact shared release source.

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.

Reproducible builds / signing

Normal F-Droid signing is intentionally requested and accepted by the upstream maintainer. Play and F-Droid will use different certificates for the same application ID; switching channels requires manual backup, uninstall and restore.

The published Play artifact remains immutable. The first F-Droid source adds license assets and replaces a donation-service logo with original artwork, so it is not claimed to reproduce that signed Play artifact.

Two local F-Droid builds were byte-identical, but this is same-environment repeatability, not independent reproducible-build verification. Binaries and AllowedAPKSigningKeys are therefore intentionally absent.

ABI splitting

Not applicable for this release. The universal APK is 12,800,626 bytes. All four ABIs' native entries together occupy only 202,140 compressed bytes, so splitting would save less than 0.2 MiB per APK.

Validation

The current fork pipeline passed, including fdroid build, source/APK checks, lint, rewritemeta, schema validation and checkupdates:

https://gitlab.com/cesar.orti1997/open-jump/-/pipelines/2914841176

Edited by Cesar Orti

Merge request reports

Loading
Loading