nomad-days

Releasing

Identity (fixed once published)

   
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

Each release

  1. Bump expo.version in app.json, plus android.versionCode and ios.buildNumber (both +1).
  2. Add 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.
  3. Run npm run test:unit && npm run typecheck && npm run rules:check.
  4. Merge to main, then tag the merge commit by its full hash: 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.
  5. Build for the stores with EAS: npx eas-cli@latest build --platform all --profile production, then npx eas-cli@latest submit --profile production.

EAS build profiles (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.

Still to do before the first release

Store screenshots

npm 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.

F-Droid

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:

What has been checked, and how to check it again after dependency upgrades:

Opening the merge request

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.

  1. Fork https://gitlab.com/fdroid/fdroiddata on GitLab and clone your fork.
  2. Create a branch named io.github.starboardhome.nomaddays and copy the recipe to metadata/io.github.starboardhome.nomaddays.yml.
  3. Run fdroid lint io.github.starboardhome.nomaddays and fdroid rewritemeta io.github.starboardhome.nomaddays. Install the tools with pip install fdroidserver, ideally in a virtualenv.
  4. Commit with the message 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.
  5. If the pipeline’s build fails, fix the recipe on the branch. Mirror any fix back into docs/fdroid/.
  6. If you release while the merge request is open, update its recipe to the new tag (versionName, the three versionCodes and commits, CurrentVersion*) and leave a short note. Reviewers asked for this.

Expect the reviewers to ask about the following: