Reading on Mobile¶
The mobile app is deliberately small. It gives members an Audience home (Continue + contents), an article reader, and a keyboard-aware Ask field. That is the whole experience on a phone.
Lessons are not on mobile yet¶
This is the important thing to know, and we would rather say it plainly than let you find out.
The lesson player is web and MCP only. Mobile keeps the reading experience: it shows you the articles, and that is all it does. You cannot attempt an exercise, submit an answer, or finish a lesson from the phone, and nothing you do on mobile moves your progress.
So mobile is where you look something up, not where you learn it. Finish a lesson on the web app or through a connected agent, and use mobile for the article afterwards.
Mobile is stricter about this than the web app. On web, an article is always readable in full whether or not you have finished its lesson. On mobile, an entry whose lesson is still waiting for you shows a full-screen notice instead of the article — Finish the lesson first — with a Continue on the web button, because there is no lesson player here to do the work with. Once the lesson is finished, or in an Audience you own, the whole article is yours to read here.
For the conceptual model, see Working Through Lessons, Reading Articles, and Asking Questions.
The contents screen¶
Opening the app drops you straight into the first Audience you belong to — there is no list screen in between. Its home shows the Audience name, a Continue card, then the contents — the entries its owner commissioned, grouped by what each article is for: Learn by doing, Get something done, Look something up, and Understand why. Anything still being written sits under Being written, and a group with nothing in it is not shown.
Each row shows the entry's name, the prompt it was commissioned from, and — when the article isn't written yet — a status chip: Queued, Writing…, Not ready, or Failed. A written article gets no chip. Mobile shows nothing about your lesson progress or mastery; that lives on the web app, where the lessons are.
The Continue card at the top points at the first entry whose article is written, labeled Continue reading. When nothing is written yet it points at the next entry on its way, wearing that entry's status instead. It shows the entry's name and prompt either way.
Pull down to refresh if you're expecting something new. At the bottom is the Ask field (the Q&A footer), scoped to the whole Audience — same grounding rules as web, single-shot on mobile.
If you belong to more than one Audience, tap the Audience's name in the header to switch: a sheet slides up listing every Audience you belong to, each with a badge showing your role in it (owner or learner). Each Audience has independent contents.
Reading an article¶
Tap any row to open its entry. A written article you have earned is rendered as a single scrolling page: read it top to bottom, and that is the whole interaction.
An entry you open may show a notice instead:
- Lesson not finished — you haven't completed this entry's lesson, and mobile can't run it. The screen says Finish the lesson first and offers Continue on the web; come back once you've finished it and the whole article will be waiting.
- Still being written — the screen shows a writing state and picks the document up as soon as it lands, without you having to leave and come back.
- Not ready — Mention could not write this article from the sources your organization has connected. The screen says why, and a What was asked for panel shows the prompt the entry was commissioned from, so you can see what material is missing. Tell your Audience's owner; connecting that material is what unblocks it.
- Write failed — something went wrong producing the document. Your Audience's owner can ask Mention to write it again from the web app.
At the bottom of every article screen is the same Ask field, scoped to the Audience.
Progress and sync¶
Mobile records no progress and shows none — not because your progress doesn't exist, but because the things it gates (which article a row opens) are checked fresh from the same account the web app writes to. Finish a lesson on web, come back to mobile, and the article opens.