OpenDataEnsemble · r0ssing · Aug 31, 2026 · Aug 31, 2026 · Sep 1, 2026
diff --git a/docs/collector/collector-getting-started.md b/docs/collector/collector-getting-started.md
@@ -17,33 +17,25 @@ Before starting, make sure you have:
 
 ## Step 1: Install Formulus
 
-### Option A: From Google Play Store (Android)
+### Option A: F-Droid (Android)
 
-1. Open **Google Play Store** on your Android phone
-2. Search for **"Formulus"**
-3. Tap **Install**
-4. Wait for installation to complete (usually 1-2 minutes)
+1. Open the [Formulus page on F-Droid](https://f-droid.org/en/packages/org.opendataensemble.formulus/)
+2. Install the F-Droid client if prompted
+3. Tap **Install** and wait for the download to complete
 
-### Option B: From App Store (iOS)
+### Option B: App Store (iPhone and iPad)
 
-1. Open **App Store** on your iPhone
-2. Search for **"Formulus"**
-3. Tap **Get**
-4. Authenticate with Face ID, Touch ID, or Apple ID
-5. Wait for installation to complete
+1. Open the [Formulus App Store page](https://apps.apple.com/dk/app/formulus/id6798318215)
+2. Tap **Get**
+3. Authenticate with Face ID, Touch ID, or Apple ID
+4. Wait for installation to complete
 
-### Option C: Direct Installation (Android)
+### Option C: Obtainium or direct APK (Android)
 
-If your project manager provided an APK file:
-
-1. Download the APK file to your phone
-2. Open your file manager and locate the APK
-3. Tap the file to install
-4. If prompted, allow installation from "Unknown Sources"
-5. Tap **Install**
+Use [Obtainium](https://github.com/ImranR98/Obtainium) with `https://github.com/OpenDataEnsemble/ode` for updates from GitHub Releases, or download the APK directly from [Downloads](/downloads).
 
 :::note
-If you don't have Google Play Store access or need a specific version, contact your project manager for a direct download link.
+The [Downloads](/downloads) page has the current Android APK and all desktop/CLI downloads.
 :::
 
 ## Step 2: Open Formulus & Connect to Your Project

diff --git a/docs/development/architecture.md b/docs/development/architecture.md
@@ -223,6 +223,7 @@ See [Security reference](/docs/reference/security) for deployment checklist and
 
 - **Local Database**: Fast queries using WatermelonDB
 - **Incremental Sync**: Only sync changes since last sync
+- **Adaptive pages**: Formulus starts at 32 pull / 4 push, grows toward 500 / 100, floor 1
 - **Lazy Loading**: Load attachments on demand
 - **Caching**: Cache app bundles and form specifications
 

diff --git a/docs/development/building-testing.md b/docs/development/building-testing.md
@@ -234,10 +234,14 @@ The project uses GitHub Actions for continuous integration:
 ### Workflows
 
 **Synkronus Docker Build:**
-- Triggers on push to `main` or PRs affecting `synkronus/`
-- Builds Docker image
-- Publishes to GitHub Container Registry
-- Tags: `latest`, `v{version}`, `{branch-name}`
+- Builds on relevant pushes to `main` or `dev`, pull requests, published GitHub Releases, and manual dispatches
+- Publishes multi-platform images to GitHub Container Registry (pull requests build without publishing)
+- Stable releases publish `v{version}`, major/minor pointers, and `latest`
+- Pre-releases publish `v{version}-{pre}` and `latest-pre-release`
+- Branch pushes publish `main` or `dev` plus an immutable `sha-{short}` tag
+- Manual dispatches publish only `sha-{short}`; feature-branch images are not published automatically
+
+See the [Deployment guide](/docs/guides/deployment) for the image-tag channels and recommended uses.
 
 **Frontend Quality Checks:**
 - Runs on all PRs

diff --git a/docs/development/installing-formulus-dev.md b/docs/development/installing-formulus-dev.md
@@ -161,19 +161,19 @@ adb install app-debug.apk
 
 ```bash
 # Browse the release and download the arm64-v8a APK for most phones:
-# https://github.com/OpenDataEnsemble/ode/releases/tag/v1.3.0
-# Asset names look like: formulus-v1.3.0-35-arm64-v8a-release-YYYYMMDD.apk
-adb install /path/to/formulus-v1.3.0-*-arm64-v8a-release-*.apk
+# https://github.com/OpenDataEnsemble/ode/releases/tag/v1.3.2
+# Asset names look like: formulus-v1.3.2-64-universal-release-YYYYMMDD.apk
+adb install /path/to/formulus-v1.3.2-*-universal-release-*.apk
 ```
 
   </TabItem>
   <TabItem value="windows" label="Windows">
 
 ```powershell
 # Browse the release and download the arm64-v8a APK for most phones:
-# https://github.com/OpenDataEnsemble/ode/releases/tag/v1.3.0
-# Asset names look like: formulus-v1.3.0-35-arm64-v8a-release-YYYYMMDD.apk
-adb install "C:\path\to\formulus-v1.3.0-*-arm64-v8a-release-*.apk"
+# https://github.com/OpenDataEnsemble/ode/releases/tag/v1.3.2
+# Asset names look like: formulus-v1.3.2-64-universal-release-YYYYMMDD.apk
+adb install "C:\path\to\formulus-v1.3.2-*-universal-release-*.apk"
 ```
 
   </TabItem>

diff --git a/docs/getting-started/architecture-overview.md b/docs/getting-started/architecture-overview.md
@@ -6,7 +6,7 @@ sidebar_position: 1
 
 ODE (Open Data Ensemble) is a comprehensive platform for mobile data collection and synchronization. This guide explains the core architecture and components.
 
-> **Current ODE release:** [v1.3.0](https://github.com/OpenDataEnsemble/ode/releases/tag/v1.3.0)
+> **Current ODE release:** [v1.3.2](https://github.com/OpenDataEnsemble/ode/releases/tag/v1.3.2) · [Downloads](/downloads)
 
 ## Core Components
 

diff --git a/docs/getting-started/faq.md b/docs/getting-started/faq.md
@@ -6,7 +6,7 @@ sidebar_position: 5
 
 Common questions about ODE installation, usage, and development.
 
-> **Current ODE release:** [v1.3.0](https://github.com/OpenDataEnsemble/ode/releases/tag/v1.3.0) (Synkronus container, Formulus APK, Desktop, Portal)
+> **Current ODE release:** [v1.3.2](https://github.com/OpenDataEnsemble/ode/releases/tag/v1.3.2) (Synkronus container, Formulus, Desktop, CLI, Portal) · [Downloads](/downloads)
 
 ## General Questions
 

diff --git a/docs/getting-started/installation.md b/docs/getting-started/installation.md
@@ -11,15 +11,16 @@ To run ODE you need two things: a **server** (Synkronus) that stores and syncs d
 | Component | What it is | Guide |
 |-----------|------------|--------|
 | **Server (Synkronus)** | Backend that hosts the API, portal, and database. Runs on a Linux server or VPS. | [Install Synkronus](installation/installing-synkronus) |
-| **Client (Formulus)** | Mobile app for Android that field workers use to fill forms and sync data. | [Install Formulus](installation/installing-formulus) |
+| **Client (Formulus)** | Mobile app for Android and iOS that field workers use to fill forms and sync data. | [Install Formulus](installation/installing-formulus) |
 
 Install the server first so that the client has something to connect to. Then install Formulus (or your client app) on each device and point it at your Synkronus server.
 
 ## For IT / infrastructure teams
 
-Hosting Synkronus for a study? See **[Server Architecture for IT](/docs/guides/server-architecture-for-it)** for a one-page overview: container layout, TLS, backups, and how custom apps (app bundles) relate to the server. Current platform release: **v1.3.0**.
+Hosting Synkronus for a study? See **[Server Architecture for IT](/docs/guides/server-architecture-for-it)** for a one-page overview: container layout, TLS, backups, and how custom apps (app bundles) relate to the server. Current platform release: **v1.3.2**.
 
 ## Next steps
 
 - **[Install Synkronus](installation/installing-synkronus)** — Set up the server on a Linux machine or VPS.
-- **[Install Formulus](installation/installing-formulus)** — Put the Formulus app on Android devices and connect it to your server.
+- **[Downloads](/downloads)** — Get Formulus, ODE Desktop, or the Synkronus CLI for your platform.
+- **[Install Formulus](installation/installing-formulus)** — Put the Formulus app on Android or iOS devices and connect it to your server.
diff --git a/docs/getting-started/installation/installing-formulus.md b/docs/getting-started/installation/installing-formulus.md
@@ -4,15 +4,16 @@ sidebar_position: 2
 
 # Installing Formulus App
 
-Complete guide for installing the Formulus mobile application on Android devices.
+Complete guide for installing the Formulus mobile application on Android and iOS devices. For the current links, see [Downloads](/downloads).
 
 ## Overview
 
-Formulus is available for Android devices through multiple installation methods. Choose the method that best fits your needs:
+Formulus is available for Android and iOS. Choose the method that best fits your device:
 
-- **Obtainium** (Recommended) - Installs Formulus from GitHub releases with automatic updates. Install Obtainium via F-Droid or direct download.
-- **F-Droid** - Install Formulus directly from [F-Droid](https://f-droid.org/packages/org.opendataensemble.formulus/)
-- **Direct APK** - Download and install the APK file directly from [GitHub releases](https://github.com/OpenDataEnsemble/ode/releases) (current: **v1.3.0**)
+- **F-Droid** (recommended for Android) - Install Formulus directly from [F-Droid](https://f-droid.org/en/packages/org.opendataensemble.formulus/)
+- **Obtainium** (Android) - Installs Formulus from GitHub releases with automatic updates.
+- **Direct APK** (Android) - Download the current APK from [Downloads](/downloads) or [GitHub releases](https://github.com/OpenDataEnsemble/ode/releases).
+- **App Store** (iPhone/iPad) - Install Formulus from the [Apple App Store](https://apps.apple.com/dk/app/formulus/id6798318215).
 - **Development Build** - For developers who want to build from source
 
 ## System Requirements
@@ -22,6 +23,7 @@ Before installing, ensure your device meets these requirements:
 | Requirement | Minimum |
 |-------------|---------|
 | **Android Version** | Android 7.0 (API level 24) or higher |
+| **iOS Version** | iOS 15.1 or higher |
 | **Storage Space** | 50 MB free space |
 | **Internet Connection** | Required for initial setup and synchronization |
 | **Permissions** | Camera, Storage, Location (for form features) |
@@ -86,7 +88,7 @@ You have two options to install Obtainium:
 
 ![Obtainium Add App Screen](/img/installation/obtainium-add-app.png)
 
-**Stable release:** Install **v1.3.0** (or the latest [GitHub release](https://github.com/OpenDataEnsemble/ode/releases)). Pre-release toggles are only needed for alpha/beta testing.
+**Stable release:** Install **v1.3.2** (or the latest [GitHub release](https://github.com/OpenDataEnsemble/ode/releases)). Pre-release toggles are only needed for alpha/beta testing.
 
 #### Step 3: Install Formulus
 
@@ -97,7 +99,7 @@ You have two options to install Obtainium:
    - App name: **ode**
    - Developer: **OpenDataEnsemble**
    - Package: `org.opendataensemble.formulus`
-   - Latest version: **v1.3.0** (or current [release](https://github.com/OpenDataEnsemble/ode/releases))
+   - Latest version: **v1.3.2** (or current [release](https://github.com/OpenDataEnsemble/ode/releases))
    - Status: **Not installed**
 5. **Tap the "Install" button** at the bottom of the screen
 6. **Confirm installation** when prompted:
@@ -127,7 +129,7 @@ Obtainium will automatically check for updates:
 5. **Confirm the update** when prompted
 6. **App data is preserved** during update
 
-### Method 2: F-Droid
+### Method 2: F-Droid (recommended for Android)
 
 Install Formulus directly from F-Droid (no Obtainium required):
 
@@ -136,13 +138,13 @@ Install Formulus directly from F-Droid (no Obtainium required):
 3. Tap **Install** and wait for the download to complete
 4. Updates are available through F-Droid when a new version is published
 
-### Method 3: Direct APK Installation
+### Method 3: Direct APK Installation (Android)
 
 If Obtainium is not available or you prefer direct installation:
 
 #### Step 1: Download the APK
 
-1. **Download the latest APK** from the [releases page](https://github.com/OpenDataEnsemble/ode/releases)
+1. **Download the latest APK** from [Downloads](/downloads) or the [releases page](https://github.com/OpenDataEnsemble/ode/releases)
 2. **Save the file** to your device's Downloads folder
 
 #### Step 2: Enable Unknown Sources
@@ -165,7 +167,13 @@ If Obtainium is not available or you prefer direct installation:
 6. **Wait for installation** to complete
 7. **Tap "Open"** to launch the app
 
-### Method 4: Development Build
+### Method 4: App Store (iPhone and iPad)
+
+1. Open the [Formulus App Store page](https://apps.apple.com/dk/app/formulus/id6798318215) on your iPhone or iPad.
+2. Tap **Get**, then authenticate with Face ID, Touch ID, or your Apple ID.
+3. Wait for Formulus to install, then open it from your home screen.
+
+### Method 5: Development Build
 
 For developers who want to build and install from source, see the [Development Installation Guide](/docs/development/formulus-development).
 
@@ -273,7 +281,7 @@ To verify that Formulus is installed correctly:
 
 ### Via Direct APK
 
-1. **Download the latest APK** from the [releases page](https://github.com/OpenDataEnsemble/ode/releases)
+1. **Download the latest APK** from [Downloads](/downloads) or the [releases page](https://github.com/OpenDataEnsemble/ode/releases)
 2. **Install over existing installation** (no need to uninstall)
 3. **App data is preserved** during update
 

diff --git a/docs/getting-started/installation/installing-ode-desktop.md b/docs/getting-started/installation/installing-ode-desktop.md
@@ -6,9 +6,9 @@ sidebar_position: 3
 
 Complete guide for installing **ODE Desktop** on Windows, macOS, and Linux.
 
-:::info ODE v1.1.0
+:::info ODE v1.3.2
 
-ODE Desktop is part of the **ODE v1.1.0** release. Pre-built installers are published on [GitHub Releases](https://github.com/OpenDataEnsemble/ode/releases).
+ODE Desktop is part of the **ODE v1.3.2** release. Use the [Downloads](/downloads) page for direct, platform-matched installers or browse [GitHub Releases](https://github.com/OpenDataEnsemble/ode/releases).
 
 :::
 
@@ -36,8 +36,8 @@ Choose the installation method that fits your role:
 
 ## Method 1: GitHub Releases (recommended)
 
-1. Open [OpenDataEnsemble/ode releases](https://github.com/OpenDataEnsemble/ode/releases).
-2. Select the **v1.1.0** release (or the latest stable tag).
+1. Open [Downloads](/downloads) to download the installer matched to your platform, or open [OpenDataEnsemble/ode releases](https://github.com/OpenDataEnsemble/ode/releases).
+2. Select the **v1.3.2** release (or the latest stable tag).
 3. Download the artifact for your platform:
 
    | Platform | Typical artifact |

diff --git a/docs/guides/deployment.md b/docs/guides/deployment.md
@@ -13,7 +13,7 @@ Complete guide to deploying ODE in production environments using containers (Doc
 
 ODE production deployments center on the **Synkronus container image** (`ghcr.io/opendataensemble/synkronus`). The reference stack is [synkronus-quickstart](https://github.com/OpenDataEnsemble/synkronus-quickstart): Synkronus, PostgreSQL, and **Caddy** for TLS. Your IT team may use any hardened reverse proxy (Nginx, Apache, cloud load balancer) instead of Caddy—the requirement is **TLS termination** forwarding to Synkronus on port 8080.
 
-Pin the image tag in production (e.g. `ghcr.io/opendataensemble/synkronus:v1.3.0`), not `:latest`.
+Pin the image tag in production (e.g. `ghcr.io/opendataensemble/synkronus:v1.3.2`), not `:latest`.
 
 ## Recommended Production Setup
 
@@ -160,20 +160,43 @@ services:
 
 Pre-built images are automatically published to GitHub Container Registry (GHCR) via CI/CD.
 
-### Pull the Latest Image
+### Choose an Image Tag
+
+Choose a deployment tag based on the update channel you want:
+
+| Tag | What it tracks | Recommended use |
+|-----|----------------|-----------------|
+| `latest` | Most recently published **stable** GitHub Release | Production deployments that intentionally auto-update between stable releases |
+| `latest-pre-release` | Most recently published GitHub Release marked **pre-release** | Demo/staging deployments and Watchtower-managed pre-release testing |
+| `dev` | Tip of the `dev` branch | Bleeding-edge integration testing; may contain unpublished work |
+| `main` | Tip of the `main` branch | Testing current main between releases |
+| `v1.2.3-alpha.4` | One specific pre-release | Reproducible pre-release deployment; does not auto-update |
+| `v1.2.3` | One specific stable release | Reproducible production deployment; does not auto-update |
+| `sha-abc1234` | One specific commit | Debugging or exact-build reproduction; does not auto-update |
+
+`dev` is a branch-head channel, **not** the published pre-release channel. To track published alpha or release-candidate images, use `latest-pre-release`:
 
 ```bash
-docker pull ghcr.io/opendataensemble/synkronus:latest
+docker pull ghcr.io/opendataensemble/synkronus:latest-pre-release
+```
+
+Versioned and moving release tags are produced only when a GitHub Release is **published**. Merely pushing a Git tag is not enough, and the release must be marked as a pre-release for `latest-pre-release` to move. Publishing a stable release updates `latest` but does not update `latest-pre-release`; there is no single tag that tracks the newest release regardless of whether it is stable or pre-release.
+
+Feature-branch images are not published automatically. A manually dispatched workflow run publishes only an immutable `sha-{short}` tag and does not move `latest`, `latest-pre-release`, `main`, or `dev`.
+
+### Automatic Updates with Watchtower
+
+Watchtower follows the tag configured on the running container. For a demo server that should receive each published pre-release, configure the Synkronus service with the moving pre-release tag:
+
+```yaml
+services:
+  synkronus:
+    image: ghcr.io/opendataensemble/synkronus:latest-pre-release
 ```
 
-### Available Tags
+Use `latest` instead to follow stable releases. Do not use a versioned tag such as `v1.2.3-alpha.4` if you expect automatic upgrades; versioned and `sha-*` tags identify fixed builds.
 
-| Tag | Description |
-|-----|-------------|
-| `latest` | Latest stable release from main branch |
-| `v1.0.0` | Specific version tags |
-| `develop` | Development branch (pre-release) |
-| `feature-xyz` | Feature branches (pre-release) |
+For production, pin a tested version tag and perform controlled upgrades rather than relying on an automatically moving tag.
 
 ### Run Pre-built Image
 
@@ -432,6 +455,10 @@ sudo ufw enable
 
 ## Performance Tuning
 
+### Reverse proxy timeouts
+
+Field sync, photo upload, and app-bundle download can run for minutes on slow radio. The bundled [`nginx.conf`](https://github.com/OpenDataEnsemble/ode/blob/main/synkronus/nginx.conf) sets `proxy_send_timeout` and `proxy_read_timeout` to **600s**. If you use Caddy, Apache, or an institutional load balancer, set equivalent send/read (or idle) timeouts to at least 10 minutes. Leave login/refresh on the default short path — Synkronus already bounds `/api/auth/*` at 25s.
+
 ### PostgreSQL Optimization
 
 Add to `docker-compose.yml` under postgres service: