Claude Products: App, Desktop, Mobile, Chrome and Code

Claude is one assistant available through several products. They share your account, your conversation history and (depending on plan) your Projects, Memory and connectors, but each surface has a different job. The exam tests whether you can name the surfaces, state what each is for, and pick the right one for a scenario. Feature availability changes frequently and varies by plan and region, so this lesson describes the shape of each product and points you to support.claude.com for current detail.

The web app (claude.ai)

The browser version is the reference experience and the one most people start with. It offers the full conversational feature set: model selection (on paid plans), file uploads, web search, Research, Projects, Artifacts, Styles, Memory, connectors to workplace tools, and the settings where you manage privacy and capabilities. If a feature exists, it is almost always in the web app first. For most desk-based knowledge work, the web app is the default choice.

The desktop apps (macOS and Windows)

The desktop app mirrors the web app and adds things only a locally installed program can do:

• a global keyboard shortcut to summon Claude over whatever you are working on;
• quick capture of screenshots or selected text into a chat;
• dictation;
• local connectors: the desktop app can run connectors (MCP servers) on your own machine, which lets Claude read local files or talk to desktop software your organisation approves;
• an agentic working mode, introduced as Cowork, in which you point Claude at a folder and give it a multi-step task (sort these files, build a report from these spreadsheets, draft replies to these documents). Claude plans, works through the task and asks for confirmation at key points. It is designed for non-developers who want Claude to do work rather than only answer questions.

Cowork is the business-user counterpart to Claude Code and has been rolling out progressively across plans; check availability for your plan.

The mobile apps (iOS and Android)

Mobile is for Claude away from the desk. Your chats and Projects sync, and the apps add:

• voice mode for spoken, hands-free conversations;
• camera input, so you can photograph a whiteboard, a receipt or a page of a document and ask about it;
• share-sheet integration to send a web page, image or file to Claude from another app;
• dictation and widgets for fast capture.

Typical uses: preparing for a meeting in transit, capturing notes after a site visit, a quick fact check, or drafting a reply you will polish later at a desk.

Claude in Chrome

Claude in Chrome is a browser extension that puts Claude in a side panel with the ability to see and act on web pages. Unlike the chat app, it can navigate sites, click, fill forms, read across tabs and complete multi-step tasks on your behalf: comparing products across retailer sites, filling an expense form from a receipt, gathering information from several internal web tools into a summary. It is agentic, which brings controls: you grant permission per site, Claude asks before taking consequential actions such as purchases or submissions, and certain categories of site are blocked by default. It started as a limited research preview and has widened over time; availability depends on plan.

Claude Code

Claude Code is Anthropic's agentic tool for software development. It runs in a terminal, inside code editors, as a desktop interface and on the web, and it reads, writes and runs code in a developer's project. For the CCAO-F exam you need to know what it is and who it is for, not how to use it. If a scenario involves writing or changing software, Claude Code is the answer; if it involves documents, data or workflows for a non-technical team, it is not.

Claude inside other tools

Claude also appears inside products people already use: an app for Slack, add-ins for spreadsheet and presentation software, and connectors that let Claude read and act on tools such as Google Workspace, Microsoft 365, Notion, Jira and Salesforce. These are covered in Domain 4; the point here is that "using Claude" does not always mean opening claude.ai.

Matching surface to situation

You are...	Best surface
Working through a document-heavy task at a desk	Web or desktop app
Repeating a task across many files on your computer	Desktop app (agentic mode)
Travelling, in a meeting, or capturing something physical	Mobile app
Completing a task that lives on websites or web forms	Claude in Chrome
Writing or changing software	Claude Code
Already in a chat tool or spreadsheet and want help there	The relevant integration

What stays the same across surfaces

Your account, plan, usage limits, privacy settings, Projects, Styles and Memory are shared. A conversation started on mobile can be continued on desktop. This consistency means the choice of surface is about convenience and capability, never about which "version of Claude" is smarter.

Exam focus

• The web app is the reference surface with the full feature set; desktop adds shortcuts, capture, local connectors and an agentic working mode for files on your machine.
• Mobile adds voice, camera and share-sheet capture; conversations sync across all surfaces.
• Claude in Chrome acts on web pages (navigate, click, fill forms) with per-site permissions and confirmations for consequential actions.
• Claude Code is for software development; scenarios about documents, data or non-technical workflows point elsewhere.
• Account, plan, limits, Projects, Styles and Memory are shared across surfaces; the surface changes capability and convenience, not intelligence.