The mobile app

What it is#

Projectri's phone app is a full client, not a viewer. It shares the server with the web app, so a change to what Nia can do, what a permission means or how a number is calculated reaches the phone without a new build — only changes to the screens themselves need one.

It is on every plan, including Free.

How to get there#

Install it from the App Store or Google Play and sign in with the same account. The bottom bar has six destinations: Home, My Tasks, Inbox, Nia, Chat and More. More is where the rest of the app lives, including an Admin section for administrators.

Everything is gated on the same permission keys as the web, so the app hides exactly what the browser hides.

How to use it#

The daily work#

Home is a briefing written for you from your own day, not the company's. My Tasks groups your work; a task opens full-screen with its comments, subtasks, checklists, dependencies, time, attachments and reminders. Projects, boards, notes, documents, the calendar, the knowledge base and search are all there.

Chat#

Channels and direct messages together, with threads on their own screen, voice notes, files and reactions. Device keys, approval and linking all work on the phone — see Messaging and encryption.

Nia#

Her own tab, with the same tools, voice, and a paperclip that offers the photo library, the camera and a file. On iPhone, "Hey Siri, ask Projectri…" reaches her from the lock screen with the app closed.

Time, money and delivery#

My Time and timesheets, expenses, cards, invoices, quotes, estimates, contracts, change orders, retainers, purchase orders, vendor bills, payments, tax, revenue and financials. Utilisation, capacity, the bench, demand, scenarios, levelling, staffing requests and bookings. Goals, cycles, playbooks, proofs, signatures, status reports, dashboards and saved reports.

Admin#

Under More → Admin: overview, members, teams, skills, workload, workspaces, settings, security, identity, the audit log and audit streaming, automation, agents and their approvals, AI usage, account requests, legal holds, residency, sandbox and warehouse.

Two things only the phone does#

1. App Lock. Require Face ID, Touch ID or a fingerprint to open Projectri, on top of an already-valid session. A privacy shade covers the app in the task switcher.
2. Working offline on time entries. Creating, editing and deleting a time entry works with no connection; the queue syncs when you are back. The badge shows two numbers, not one — how many are waiting, and how many have stopped waiting and need you. Folding those together is how a failed entry hides inside a badge that looks like progress.

What it affects#

• Push notifications come from the same rows as the bell, so anything that notifies you on the web notifies the handset. The badge is your real unread count and goes down as you read.
• Read aloud works with the app closed. On Android a background task speaks the notification as it lands; on iOS the spoken line arrives as the notification's own sound, played by a system process, which is why it works even force-quit.
• A session is one per platform. One web, one iOS, one Android — a slot per platform, because owning both an iPhone and an Android is ordinary. Signing in where a slot is taken offers to replace the other session. Linked devices are counted separately, capped at three.
• Deep links land where they should. A notification, a search hit or a Siri request all resolve through one path, so a link written for the web opens the right screen on the phone rather than the inbox.
• Dates, numbers and money follow your locale, and Arabic lays out right-to-left. Changing to or from Arabic needs an app restart on Android to take full effect.

On mobile#

This page is the mobile page. What it leaves to the web is below.

Limits and gotchas#

Web-only, and each for a reason:

• **The whiteboard editor, the report builder, the form builder, the template editor and the automation graph.** These are multi-pane authoring surfaces. The phone consumes what they produce — boards, reports, forms and rules are all readable — but the editor is not a small screen shrunk, it is a different product.
• The Gantt and baselines. The phone reads tasks, not schedules. Promoting or discarding a frozen plan is a decision taken while looking at the ghost bars it draws, and a list of snapshot names with no chart under it would be a screen where the consequence of every button is invisible.
• The permission grid and most one-time workspace configuration. The phone shows the result of a setting everywhere it applies; an editor for it is a screen nobody would open twice.
• Bulk exports. A 50,000-row file exists to be handed on, and a handset has nowhere to put it. Reading the audit log itself is on the phone.
• Signing up, and the plan change. Sign-up has its own native flow; buying a subscription inside the app would have to go through in-app purchase, so the web does the transaction and the phone reads the result.
• The platform console. A separate application for our own staff, not part of the tenant app at all.

Other things worth knowing:

• Push does not work on the iOS simulator. There is no Apple push service there, and the app returns nothing rather than pretending otherwise.
• A force-stopped Android app receives no notifications at all. That is the platform working as intended, not a fault.
• Only time entries queue offline. Everything else needs a connection.
• Search on the Chat tab never covers message text. An encrypted body is unreadable on the device until that conversation's key has loaded.

Related#

• The mobile app — installing it, signing in, App Lock.
• Notifications — push, read aloud and the badge.
• Nia, the assistant — the Nia tab and voice.
• Messaging and encryption — approving this device.