feat: F-Droid listing

[arunrajiah]

Summary

Get BirdEcho listed on F-Droid so users can install it without sideloading APKs.

Steps

1. Prepare YAML metadata file for fdroid/fdroiddata
2. Ensure build is reproducible from source (expo prebuild + gradlew assembleRelease)
3. Declare any anti-features (Sentry optional telemetry)
4. Submit PR to https://gitlab.com/fdroid/fdroiddata
5. Respond to F-Droid maintainer review

Open questions

• Does Expo's managed workflow produce reproducible Gradle output?
• Does optional Sentry require the NonFreeNet anti-feature tag?

Acceptance criteria

• App appears in F-Droid repository
• Installs and runs correctly from F-Droid client

[arunrajiah]

Status update

F-Droid submission groundwork is complete in docs/fdroid/:

• docs/fdroid/dev.arunrajiah.birdecho.yml — full F-Droid YAML metadata (package name, license, build recipe including expo prebuild, scanignore for node_modules, AntiFeatures: Tracking for Sentry)
• docs/fdroid/SUBMISSION_NOTES.md — documents the three main blockers and recommended path

Recommended first step: IzzyOnDroid
Full fdroid/fdroiddata has three hard blockers (no committed android/ directory, non-reproducible Expo/Hermes builds, Sentry anti-feature). IzzyOnDroid accepts pre-built APKs from GitHub Releases and is the fastest path to users who prefer not to sideload manually.

To submit to IzzyOnDroid: open an issue at https://gitlab.com/IzzyOnDroid/repo/-/issues with a link to the latest release APK on GitHub Releases.

Full F-Droid (fdroiddata): viable once either (a) android/ is committed and the build is proven reproducible, or (b) F-Droid adds support for Expo-managed prebuild pipelines. The YAML recipe in docs/fdroid/ is ready to paste into a PR when that path is clear.

[arunrajiah]

F-Droid metadata updated to v0.5.0 — commit deabef2.

What changed in docs/fdroid/

File	Change
dev.arunrajiah.birdecho.yml	Filled in real commit SHAs for v0.3.1, v0.3.2, v0.5.0; added build entries for v0.3.2 (vc 10) and v0.5.0 (vc 13); updated CurrentVersion/CurrentVersionCode to 0.5.0/13; expanded v0.5.0 scanignore with expo-file-system, expo-notifications, react-native-android-widget, react-native-maps; updated prebuild: to strip projectId from app.config.ts (active config since v0.3.3); expanded Description with new features; added MaintainerNotes for the Google Maps key absence
SUBMISSION_NOTES.md	Promoted IzzyOnDroid fast-path to the top with step-by-step instructions; updated checklist to reflect that commit SHAs are now filled in

Recommended immediate action: IzzyOnDroid

The single fastest unblocking step is to open an issue at https://gitlab.com/IzzyOnDroid/repo/-/issues requesting inclusion. IzzyOnDroid takes the pre-built APK directly from GitHub Releases — no source build, no android/ directory, no Gradle setup needed. Once there, users can install without sideloading and receive update notifications.

Remaining blockers for full fdroiddata

1. Node 24 tarball SHA-256 — the sudo: block still has REPLACE_WITH_SHA256_FROM_NODEJS_ORG. Get the hash from https://nodejs.org/dist/latest-v24.x/SHASUMS256.txt and fill it in (all three build entries).
2. android/ not committed — the biggest blocker. Options: commit the prebuild output to an fdroid branch and point commit: there, or rely on the init: prebuild steps and verify it works via fdroid build --on-server.
3. Sentry decision — keep Tracking anti-feature or uncomment the strip line.
4. react-native-maps/android/libs rm entry — verify this directory actually exists after expo prebuild at v0.5.0; remove the entry if it doesn't.