Mobile App
The mobile app is the end-user client for ThinkWork. Where the Admin Web App is for operators configuring a tenant, the mobile app is for the people actually doing work inside the tenant — chatting with agents, reviewing threads, answering agent confirmation requests, acting on external tasks, and connecting their own integrations.
It’s an Expo application built on React Native, Expo Router, and the same GraphQL + REST endpoints the admin app uses. It is currently shipping on iOS via TestFlight.
Who uses it
Section titled “Who uses it”End users inside a tenant. That can mean:
- A knowledge worker chatting with an agent for research or drafting
- A frontline operator working through a Tasks tab of external tasks routed from a task system
- A human reviewer approving, continuing, or rejecting an agent run that paused for confirmation
- A specialist connecting their personal Google account so an agent can read their calendar or email
- An on-call engineer receiving a push notification when a task is assigned to them
The mobile app is deliberately focused — it is not a miniature of the admin app. It only exposes what an individual user needs to do their own work.
The three tabs
Section titled “The three tabs”The root layout is a three-tab structure with deep-link support for additional screens:
| Tab | Purpose |
|---|---|
| Threads | Thread list, filtering, message input, and agent confirmation requests. Doubles as the entry point for starting new work |
| Tasks | External task list — only visible when a task connector is connected |
| Settings | Account, integrations, MCP servers, push notifications, theme, biometric lock |
From any tab, the user can drill into a thread detail screen (/thread/[threadId]) which is where chat happens. The message input supports workspace selection, voice dictation, and quick actions.
Guide layout
Section titled “Guide layout”This section splits the mobile app into five sub-pages:
- Authentication — Google OAuth, biometric lock, session restore, the pre-signup Lambda
- Threads & Chat — Threads tab, thread detail, HITL review cards, streaming render, message input, quick actions
- Integrations & MCP Connect — self-serve OAuth for connectors and MCP servers
- Push Notifications — registration, payload handling, deep linking
- Distribution — EAS channels, TestFlight, iOS build setup
What the mobile app is not
Section titled “What the mobile app is not”Deliberate non-goals worth naming:
- Not an admin console. Tenant configuration, agent authoring, guardrails, and analytics live in the Admin Web App.
- Not a general-purpose chat app. Conversations are always with an agent (or a routine), never user-to-user. There are no DMs, no channels, no group chats.
Platform status
Section titled “Platform status”| Platform | Status |
|---|---|
| iOS (TestFlight) | Beta — live for early users |
| Android | Not yet shipped — the Expo code is cross-platform, but no production Android build is published |
| Web (Expo web) | Not a target — the Admin Web App covers the browser use case |
The v1 focus is iOS. Android follows once the iOS shape is stable.
Related pages
Section titled “Related pages”- Admin Web App — the operator-facing control plane
- CLI —
thinkwork-clifor deployment - MCP Tools — the MCP model the mobile app connects into