On your phone

Open DraftMesh in a phone browser and you get a layout built for a phone rather than a shrunken desktop window. It is a review surface: the work that arrives in bursts — sign-offs, replies, suggestions to accept or reject — done with a thumb, in a queue.

Long-form writing stays on the desktop layout. There is no rich-text editor here by design.

Getting the phone layout (or leaving it)

DraftMesh picks the layout from the width of your screen. An explicit choice overrides that, and is remembered on this device from then on:

• Me tab → Layout → Use the desktop layout switches to the full app.
• Adding ?surface=mobile or ?surface=desktop to the address forces one, and is likewise remembered until you change it.

Inbox — the things waiting on you

The Inbox is the home tab: everything in the open workspace that names you, newest first. An item lands here when someone asks you to sign off, assigns you a comment, mentions you, replies to a thread you started, or leaves you a question.

Filter chips across the top — All, Approvals, Comments, Suggestions — narrow the queue, and each chip carries its own count.

Approval rows carry two buttons:

• Approve signs off without opening the document. The request names the exact version you’re signing, so this is a real decision, not a shortcut past one.
• Review first opens the sign-off review screen below.

Under the queue, Done today is a receipt strip of what you’ve already cleared. A tick means the write actually landed; a plain dot means it’s still in flight; anything that failed says so in words rather than pretending it went through.

Tapping the workspace name at the top of the Inbox switches workspaces. The queue is always the open workspace’s.

Nothing is sent the instant you tap

Every action is queued rather than sent straight away, and the ones you’re most likely to regret — Approve, a reply, a new comment, Request changes — sit for about five seconds behind an Undo button in the toast. Undo inside that window is a local drop: the write never happened at all.

The deliberate endings — resolving a thread, accepting or rejecting a suggestion, sending a suggestion of your own — go without the undo window, because each of them is already the confirming tap.

Leaving the screen, taking another action, or backgrounding the browser sends a queued action immediately rather than waiting out the timer. If a send fails, the item comes back into your queue with a Retry — nothing is quietly lost, and the Done today strip says “didn’t send” rather than showing a tick.

Reviewing a sign-off request

Tapping an approval item opens the review screen, which shows what changed since you last approved this document rather than the whole file again — with the version you’re comparing against named in the band at the top. Your first sign-off on a document shows it in full, as does a document too large to compare change by change; the screen says which of those you’re looking at.

• Approve records the decision, pinned to the version you just read.
• Request changes opens a sheet for a note explaining what should change first.

If the document moved underneath you between opening it and deciding, DraftMesh refuses the decision rather than attaching your name to prose you didn’t read.

Reviewing a suggestion

A suggestion item shows the proposed replacement against the current text, with Accept edit and Reject. If the text a suggestion anchored to has changed too much to apply automatically, the screen says so instead of guessing.

Replying to a comment

Tapping a comment or question opens the thread sheet: the whole discussion, a composer, and Resolve. Quick-reply chips offer the common answer for that kind of marker — they fill the composer rather than sending, so nothing goes out over your name that you didn’t read first. Type @ to mention someone.

Resolve is disabled while you have text in the composer: resolving is not a place for a reply to disappear into.

Reading a document

Open a document from the Docs tab or Search. (Inbox items open the review screen or the thread directly, not the whole document.) The reader renders the prose with existing comments and suggestions highlighted in place; tapping a highlight opens its thread — or, for a suggestion, the accept/reject screen above. Below the prose is a list of everything open on the document, in case a marker’s text has moved.

Select any passage and a bar appears above the tab bar with Comment and Suggest — the same two acts as the desktop selection menu.

Docs and Search

• Docs browses the workspace as folders and files, with a short list at the top: the most recently edited documents where DraftMesh knows edit times, otherwise anything waiting on you followed by A–Z. The heading over the list says which of those you’re getting.
• Search matches file names as you type. Searching the text inside documents is a second, deliberate tap — Search inside documents — so a phone on a cellular connection doesn’t read the whole workspace for every keystroke. Recent searches are kept for one-tap repeats.
• Me shows who you’re signed in as, lets you switch workspaces, and holds the escape hatch back to the desktop layout.