New app: Catodon

Abstract for new app inclusion

Catodon for Android is a client for Catodon, the Misskey-lineage fediverse server software (https://codefloe.com/catodon/catodon), and works with any server running it - catodon.rocks is only the default the picker offers, not a requirement. It does not reimplement the client UI: it opens the server's own web app fullscreen, in an in-app WebView, with no browser chrome, and adds the native pieces a browser cannot provide - push notifications through a UnifiedPush distributor, share-target receiving, and deep links back into the right note.

It is not a general-purpose browser. The server picker only accepts hosts that report catodon in their NodeInfo, so every server it opens is one running the same software and the same frontend the app is built around.

Accounts from other platforms

You do not need a Catodon account to use the app. Servers that offer remote sign-in - catodon.rocks does - accept an account from another fediverse server (Mastodon, Misskey, Sharkey, Friendica and other ActivityPub implementations) in place of a local one: you authenticate on the server that actually hosts your account, and the session then talks to that server. Your posts, followers, notifications, rules and moderation stay there; nothing is copied to the Catodon server you signed in through.

The picker itself still accepts Catodon servers only, so this is the one route by which a non-Catodon account is used - it is a feature of the server the app opens, not a second kind of server the app can add.

This is the free-software, degoogled flavor of the same app that is on Google Play. It needs neither Chrome, nor Play Services, nor Google's push infrastructure: the push path uses UnifiedPush (ntfy is the reference distributor, also on F-Droid), and the shell is a plain WebView.

Screenshots

None supplied. The app displays the user's own server's web app, so a screenshot is a screenshot of that server's timeline; F-Droid does not require them and I'd rather not ship a screenshot of an arbitrary account. Happy to add them if a reviewer wants a specific view.

Why this app

There was no native Android client for Catodon. A mobile browser gives you a URL bar and a tab, and no way to receive a web push while the browser is not the focused app; this app exists to close exactly that gap, on devices that have no Play Services at all. The Play flavor does the same thing through a Trusted Web Activity and Chrome's notification delegation; that path cannot work without Google's stack, which is why the F-Droid flavor uses the UnifiedPush connector, which performs RFC 8291 decryption on the device, with no proprietary push service.

Current release

The metadata pins 1.0.2 / versionCode 5, commit v1.0.2 (annotated tag object f737b362f986e3a577ec6134ffba9ec9dd3a8855, dereferencing to 18ce382cd1c96d33847ced62ac72f4822a118ebc) on https://codefloe.com/catodon/catodon-android.

v1.0.2 is the first versionCode bump after 1.0. It carries the F-Droid push self-heal (a periodic check of the server's VAPID key and sw/show-registration), the notification-channel checks, and the Play picker note about Android's notification permission being separate from Catodon's Web Push subscription.

v1.0.1 was metadata-only: the same versionCode 4 build as v1.0, with one file changed (fastlane/metadata/android/en-US/full_description.txt, which now describes remote sign-in and the Catodon-only picker). v1.0 itself was not moved.

Checklist

Policy

  • The app complies with the inclusion policy.
  • The original app author has been notified (and does not oppose the inclusion). - I am the author and maintainer.
  • The upstream app source code repo contains the app metadata in a Fastlane folder structure (fastlane/metadata/android/en-US/: title.txt, short_description.txt, full_description.txt, changelogs/5.txt, images/icon.png).

Docs

  • I have read the contributing guide.
  • The metadata follows the template best practice; it is in the canonical form produced by fdroid rewritemeta.
  • I have read the Build Metadata Reference and the Quick Start Guide.

Merge Request Setup

  • Title follows "New app: app name".
  • Fork is public and the branch is not protected.
  • One app in one MR.
  • No RFP issue exists for this app, so nothing to reference.

Metadata

  • Metadata is in metadata/catodon.app.yml.
  • Valid YAML, LF line endings.
  • No summary/description/changelog/images in the metadata - those come from the upstream Fastlane folder. The diff is one file.
  • Releases are tagged; auto update is enabled (AutoUpdateMode: Version, UpdateCheckMode: Tags ^v[0-9.]+$).
  • AuthorName and IssueTracker are set.
  • No submodules or srclibs; everything is in the one repo.
  • Reproducible builds. The versionCode 4 F-Droid APK was verified bit-for-bit reproducible (hash recorded in docs/reproducible-builds.md); the 1.0.2 build uses the same settings, but I have not independently re-derived its hash, so please verify it with fdroid build rather than take my word for it. dependenciesInfo { includeInApk = false; includeInBundle = false } and vcsInfo.include = false keep the Google dependency blob and the git commit out of the APK, and CI builds are unsigned by design - the signing config exists only when the upload-key properties are supplied.
  • ABI splits - not applicable: there is no native code in this app.
  • Only the latest version (1.0.2, versionCode 5) is in the metadata; no disabled versions.

Regarding the checklist line "The commit field should be the full hash": the commit here is the tag v1.0.2, deliberately, because AutoUpdateMode: Version keys off tagged releases and the tag is what I sign and push alongside each release. It resolves to 18ce382cd1c96d33847ced62ac72f4822a118ebc (annotated tag object f737b362f986e3a577ec6134ffba9ec9dd3a8855) on https://codefloe.com/catodon/catodon-android. I'm happy to pin the full hash instead if you prefer that for a new app.

v1.0.1 is not a second app version: it is v1.0 (versionCode 4, versionName 1.0, unchanged) plus one file - fastlane/metadata/android/en-US/full_description.txt, which now also describes remote sign-in (an account from another fediverse server, used through a Catodon server that offers it) and states that the server picker accepts Catodon servers only. F-Droid reads that file from the tagged commit, so it had to be a later tag; v1.0 itself was not moved. v1.0.2 is the next real update: versionCode 5, with its own tag.

Pipeline

  • Pipelines pass - the 1.0.2 metadata update is being validated by CI; the previous pipeline passed. Will fix anything CI reports.
  • No warnings left in the Reports tab.
  • Understood about the FOSS CI runners.

Notes for the reviewer

  • AntiFeatures: only NonFreeNet, declared with an explanation. NonFreeDep does not apply (the F-Droid flavor's runtime classpath has no play-services/firebase/androidbrowserhelper; every dependency is Apache-2.0, MIT or similar); UpstreamNonFree does not apply (app and server are both free software, AGPL-3.0); Tracking does not apply (no analytics, crash reporting or ad SDK); NonFreeAdd does not apply (the one app it suggests installing, a UnifiedPush distributor, is free software and on F-Droid).
  • Build: subdir: app, gradle: [fdroid]. minSdkVersion 24, targetSdkVersion 36. applicationId is catodon.app in both flavors deliberately - the two flavors must not be installed side by side, since they share the same app data and the same server sessions.
  • Network: the app talks only to the server the user picks. There is no endpoint operated by the developer. NonFreeNet covers the fact that the operator of that server is a third party. When push is enabled, the app also verifies the subscription against that same server at most once every twelve hours (meta and sw/show-registration); no third-party endpoint is involved.
  • The F-Droid flavor holds the user's session token on device only after the user turns notifications on, and only to register and unregister the push subscription against their own server; android:allowBackup="false" keeps it out of cloud backups. The privacy policy is at https://catodon.rocks/@admin/pages/android-privacy-policy - it is the app-level policy (hosted on the project's own instance) and covers the app whichever server you pick, including remote sign-in.
Edited by panos

Merge request reports

Loading
Loading