> ## Documentation Index
> Fetch the complete documentation index at: https://docs.fortressproductivity.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Mobile app

> Fortress on iPhone, distributed through TestFlight.

The Fortress mobile app is the focused triage surface for working from your phone. It is built with Expo and React Native and shares Fortress API contracts with the web app.

## Navigation

The bottom tab bar carries the most common destinations: **Command** (the daily dashboard), **Tasks**, **Capture** (the center button — opens the inbox composer), **Inbox** (with the unread count badge), and **More**. The More sheet covers the rest of the app — Projects, Agents, Orders, Questions, and Documents — without leaving the current screen.

## Install via TestFlight

The iPhone app is in TestFlight while the project is in private beta. Once you have an invite:

1. Install [TestFlight](https://apps.apple.com/app/testflight/id899247664) from the App Store.
2. Open the invite link from your email. TestFlight will offer to install Fortress.
3. Launch Fortress and sign in.

Builds are delivered through TestFlight as new mobile versions ship. Public App Store release uses the same binary after promotion in App Store Connect.

## What you get

* **Quick Capture**: add a title and details directly into your Inbox.
* **Questions**: open a question to see its full context — scope, links, attached documents, and related actions — before responding from proposed answers, writing a custom answer, or dismissing it.
* **Review**: read submitted work, document revisions, and proposals; permit, edit, take over, counter, reject, complete, or drop from the phone.
* **Inbox**: clarify captured work, update the title and description, drop items you don't want to keep, and assign what's ready.
* **Badges and notifications**: app icon badges mirror your mobile attention count (Inbox plus queue), and iOS notifications appear when an agent asks a question, opens a proposal, or submits work for review.
* **Copy as Markdown**: copy IDs, status, metadata, and body text for use with an agent.

## Version numbers

The mobile app uses EAS remote versioning for developer-facing iOS build numbers so every TestFlight upload gets a fresh build number. The user-facing app version is set in `packages/mobile/app.json`.

If you need to report a bug against a specific build, include the TestFlight version and build number.

## Troubleshooting

<AccordionGroup>
  <Accordion title="The app cannot sign in">
    Update to the latest TestFlight build first. If sign-in still fails, confirm the API is reachable from your device and try signing out and back in.
  </Accordion>

  <Accordion title="A screen looks stale after an action">
    Pull to refresh or switch tabs and return. The app uses the same API data as Fortress web, so your
    change should be visible anywhere after the next refresh.
  </Accordion>

  <Accordion title="Text is hard to edit with the keyboard open">
    Update to the latest TestFlight build. Current builds keep focused fields reachable while the iOS
    keyboard is open and restore the layout after it is dismissed.
  </Accordion>

  <Accordion title="Notifications aren't appearing">
    Update to the latest TestFlight build, then confirm **Settings → Notifications → Fortress** allows notifications and badges. Production API deploys also need `APNS_TEAM_ID`, `APNS_KEY_ID`, and `APNS_PRIVATE_KEY` set in Render.
  </Accordion>
</AccordionGroup>