| App ID (iOS and Android) | io.github.starboardhome.nomaddays |
| Name | Nomad Days |
| Licence | GPL-3.0-or-later |
| Developer name | Starboard Home on Google Play and F-Droid. The App Store shows the legal name of the individual Apple Developer account (a brand name there needs an organisation account) |
| Support | GitHub Issues |
| Store text | fastlane/metadata/android/en-US/ (title, short and full description). For the App Store, paste the full description without the <b> tags |
| Export compliance | ios.config.usesNonExemptEncryption: false in app.json: encryption only protects the user’s own data (exempt), so App Store Connect doesn’t ask on each build |
| Privacy policy | https://starboardhome.github.io/nomad-days/privacy/, published from docs/PRIVACY.md by .github/workflows/pages.yml. Use this URL in the store listings |
expo.version in app.json, plus android.versionCode and ios.buildNumber (both +1).fastlane/metadata/android/en-US/changelogs/<versionCode>.txt and the same text as <versionCode>001.txt, <versionCode>002.txt and <versionCode>003.txt (500 characters at most). F-Droid publishes one APK per ABI with versionCode 1000 × code + 1/2/3 and looks changelogs up by that number. CI (scripts/ci/check-changelogs.mjs) fails if any are missing.npm run test:unit && npm run typecheck && npm run rules:check.git fetch origin && git tag v<version> <full-hash> && git push origin v<version>. F-Droid’s update checker finds the tag and builds it within a few days; no merge request is needed unless the recipe itself changes.npx eas-cli@latest build --platform all --profile production, then npx eas-cli@latest submit --profile production.eas.json)| Profile | What it builds | Use it for |
|---|---|---|
development |
Debug build: Android APK, iOS Simulator app | Running against npm run dev on another machine or a teammate’s simulator |
preview |
Release build, internal distribution (Android APK; iOS ad hoc, needs registered devices) | Testing on real phones before a release |
production |
Store build (Android App Bundle; iOS App Store) | Google Play and the App Store |
Versions come from app.json (appVersionSource: local), so bump version, android.versionCode and ios.buildNumber there. F-Droid reads the same values.
assets/source/mark.svg (groups calendar and today) on a navy #192E45 background (BACKGROUND in make-icons.cjs, plus android.adaptiveIcon.backgroundColor in app.json). After changing it, run node scripts/dev/make-icons.cjs (app icons, splash, iOS Icon Composer layer), then npm run screenshots -- --no-build (feature graphic, F-Droid icon)npm run screenshots (see below)docs/PRIVACY.md on GitHub Pages (needs Pages enabled once: Settings → Pages → Source: GitHub Actions)eas.json with development, preview and production profilesnpx eas-cli@latest init): project @starboardhome/nomad-daysnpm run screenshots (needs Playwright with Chromium: npm i -g playwright && npx playwright install chromium) builds the web app, opens six screens with the demo traveller (?demo) and frames them with captions:
| Output | Size | Upload to |
|---|---|---|
store/ios/*.png |
1320 × 2868 | App Store Connect (6.9” iPhone) |
store/android/*.png |
1080 × 1920 | Google Play phone screenshots |
store/android/feature-graphic.png |
1024 × 500 | Google Play feature graphic |
fastlane/metadata/android/en-US/images/ |
F-Droid (picked up automatically) |
Screens and captions are in SHOTS in scripts/dev/store-screenshots.cjs; the demo data is src/features/demo/demoData.ts. Re-run after UI changes. The captures come from the web build, which closely matches the apps; for pixel-exact native captures, use Settings → Developer → Load demo data in a debug build and screenshot the simulator.
The full process, every reviewer request and fix, and the mistakes to avoid are in the fdroid-release skill. Claude Code loads it automatically in this repo; read it before changing the recipe or releasing for another app.
The recipe is docs/fdroid/io.github.starboardhome.nomaddays.yml. It follows the pattern of other Expo apps in fdroiddata:
apt-get install -t forky npm), as F-Droid reviewers ask and as other Expo recipes do; it only runs at build time.buildFromSource) instead of their prebuilt AARs.build.gradle and build.gradle.kts. Modules that pin Kotlin’s jvmTarget (react-native-worklets, react-native-reanimated) otherwise fail with “Inconsistent JVM Target Compatibility”.expo prebuild, then the signing config removed so F-Droid can sign.27.1.12297006, matching React Native’s.1000 × upstream + 1/2/3. The ABI is set with printf '\nreactNativeArchitectures=…\n' and -PreactNativeArchitectures=…. expo prebuild writes gradle.properties without a final newline, so a plain echo >> glued onto expo.sqlite.useSQLCipher=true, which silently dropped both the ABI split and SQLCipher (found in F-Droid review, October 2026). Two grep -qx guards now fail the build if either property is wrong. The universal APK was 131 MB; one ABI is about 45 MB. VercodeOperation lets auto-update compute these.commit: is the full commit hash of the release tag, never the tag name (F-Droid’s template requires this).INTERNET (the app never goes online; plugins/withDebugInternet.js keeps it for debug builds so Metro works), no USE_BIOMETRIC, USE_FINGERPRINT, SYSTEM_ALERT_WINDOW or external storage (android.blockedPermissions in app.json), and R8 minify and resource shrinking on (expo-build-properties). CI checks the merged manifests and launches the R8 build on an emulator.What has been checked, and how to check it again after dependency upgrades:
fdroid lint passes, and fdroid rewritemeta leaves the file unchanged (canonical format). fdroiddata CI runs fdroidserver from master with ruamel.yaml 0.18, which wraps long lines differently from the 2.4.5 release, so check the format with pip install git+https://gitlab.com/fdroid/fdroidserver.git ruamel.yaml==0.18.10.sed matches, and android/app/build.gradle comes out with no signingConfig.node_modules (Expo AARs and JARs, the optional libSQL and sqlite-vec libraries, and the dev-only esbuild and dotslash). It ignores the Hermes compiler and four Gradle files that point at React Native’s local Maven repository.fdroid build passed on F-Droid’s CI for v1.0.5 (three per-ABI APKs with R8, merge request pipeline, 17 November 2026), and all 9 jobs pass. The scanner warns about two harmless files, an icon font and a Windows DLL that ships with the Hermes compiler; these don’t block the build. Each successful pipeline also produces a signed test APK in the fdroid build job’s artifacts.Opened for 1.0.0, then closed by F-Droid for not following the template (ticked boxes the recipe didn’t meet: tag instead of hash, no ABI split, no reproducible-builds reason, Reports warnings not explained). Fixed for 1.0.1, reviewed through 1.0.5 and merged on 17 November 2026 (fdroid/fdroiddata!51068, from the fork starboardhome/nomad-days on GitLab). Later releases need no new merge request: F-Droid finds new v* tags (UpdateCheckMode: Tags) and adds the build itself. Use these steps only if the recipe has to change.
io.github.starboardhome.nomaddays and copy the recipe to metadata/io.github.starboardhome.nomaddays.yml.fdroid lint io.github.starboardhome.nomaddays and fdroid rewritemeta io.github.starboardhome.nomaddays. Install the tools with pip install fdroidserver, ideally in a virtualenv.New app: Nomad Days, push, and open the merge request using the App inclusion template. Tick only the boxes that are true, and write the reason under any that aren’t (reproducible builds, Reports warnings). Don’t verify your GitLab account to run CI; leave a note in the merge request instead.docs/fdroid/.CurrentVersion*) and leave a short note. Reviewers asked for this.Expect the reviewers to ask about the following:
io.github.ronickg:openssl). Maven Central is an allowed repository, but they may ask.react-android, hermes-android) also come from Maven Central, as in other React Native apps on F-Droid.Binaries: and AllowedAPKSigningKeys: once our own release APK builds identically.