Mobile vs Web
Where the phone and the web app diverge: eFirm has no phone screens but its data is still reachable two ways, and the full row-by-row parity table for everything else.
Where eFirm fits on a phone
There are no eFirm screens in the mobile app. Matters, hearings, invoicing, timesheets, trust accounting, VAT, reports, KYC and HR have no phone interface, and none of the eFirm navigation exists there. That is the honest shape of the line — but it is not the same as saying eFirm is unreachable.
Two routes into your firm’s eFirm data do work from the phone:
- Through the assistant. The eFirm data actions — contacts, invoices, expenses, receipts, hearings, legal matters, milestones, tasks, files and folders, company and user settings, and cross-entity search — all run on mobile. They come back as generic action cards (see Chat on a Phone): a label-and-value or item-preview summary of what the action returned. What mobile does not have is the web’s presentation of them — no entity-specific record cards, no status or outcome badges, no type filter pills, and no click-through that opens the record in eFirm.
- Through the attach-file browser. The Storage tile in the attach sheet is a browser over the workspace’s eFirm storage, so a document already filed in eFirm can be pulled into a conversation without leaving the phone.
For the eFirm product itself, see HAQQ eFirm, which documents the web application.
Mobile against the web app
The two are the same product on the chat side and diverge at the edges. Every row below was checked on both sides rather than inferred from one.
| Capability | Web | Mobile |
|---|---|---|
| Ask, stream, and stop a response part-way through | Yes | Yes |
| Email sign-in | One-time code or link, depending on configuration | Link only — no code screen |
| Google and Microsoft sign-in | Yes | Yes |
| Sign in with Apple | — | iOS only |
| Rename and delete a conversation | Yes | Yes |
| Web search and knowledge-base results inline | Yes | Yes |
| eFirm actions run by the assistant | Yes, as record cards with status badges, filter pills and open-in-eFirm | Yes, as generic action cards — no record cards, badges, filters or click-through |
| eFirm practice-management screens | Yes | No — see the section above |
| Projects: files, instructions, sharing, archiving | Yes | Yes |
| Project create wizard, linked eFirm records, custom context, project export, project icons, drag a chat onto a project | Yes | No |
| Editing a drafted document | Rich-text editor | Markdown source editor |
| Version history on a document | Yes, with a side-by-side diff | Yes, read-only, no diff |
| Agent search, capability filters and the compare view | Yes | No |
| Setting your default agent | Yes | Read only — it is applied, not changed |
| Context-window and token-usage meters | Yes | No |
| Message density and timestamp preferences | Yes | No |
| Buying a plan or credit top-ups | Yes | In-app purchase; personal workspace and admin only |
| Camera capture, the system share sheet, push on a finished answer | — | Yes |
A dash means the row makes no claim for that platform, rather than a claim of absence. The limits a phone can actually hit — file size, message length, conversation length — are on Platform, Limits & Notifications.
Which docs pages apply on a phone
Everything under HAQQ Legal AI describes the product mobile carries, with the differences in the parity table above. Everything under HAQQ eFirm documents web screens the phone does not have, though the assistant can still read and write that data. Credits and usage applies unchanged, because the pool is shared.