One of the most underrated things about Claude is that it is not one app, it is one assistant available through several doors, and the same account follows you between them. Most people find one door and stop. Using the right door for the right moment is a genuine productivity unlock, so here are the four I use, and how I split my day across them.
The phone, for thinking out loud
The Claude mobile app has voice, and this has become my thinking tool for dead time. When I am walking or driving, I talk to Claude hands free, working through a problem out loud, dictating the bones of a proposal, or pressure testing an idea before I get back to a desk. By the time I sit down, the messy thinking is already done and captured in the chat, ready to pick up on any other device.
If you take one habit from this article, take this one. Everyone has thirty to sixty minutes a day of walking, driving, or waiting that currently produces nothing. Voice turns it into working time that does not feel like work.
Voice conversations in the Claude mobile app
The chat app, for ideas and desk work
The desktop chat app is my default at a desk for everything that is not writing code: brainstorming, drafting, analysing documents, planning, and the running strategic conversations behind each of my ventures. Chat is where ideas get shaped. I drop in files, paste in numbers, attach photos of whiteboards, and think in dialogue.
Two features make chat dramatically more useful than treating it as a smarter search box. Projects let you group related conversations and give Claude standing context about a piece of work so you are not re explaining yourself every session. And long, iterative conversations beat one shot questions, treat it like briefing a sharp colleague, give context, react to drafts, and push back.
The web version, for everywhere else
Claude at claude.ai in a browser is the same experience as the desktop app, same history, same projects. I use it in two situations: when I am on someone else's computer, and when I want a brand new feature the moment it ships, because updates sometimes land on the web before the desktop app catches up. It is also the honest answer to "do I need to install anything to try this?" No. A browser and an account is enough.
Video: starting a chat on claude.ai
The IDE and terminal, where I actually live
Now the power tool. Claude Code is Anthropic's coding harness, it runs in the terminal and inside VS Code, and it is where I spend most of my working hours building software and agentic solutions for clients. The difference from chat is the difference between advice and labour. In chat, Claude tells you how to change your code. In Claude Code, it opens the project, makes the changes across files, runs the tests, reads the failures, and fixes them, while you direct and review.
This is not just for career developers, and that is the part I want non technical readers to hear. If you can describe what you want clearly, Claude Code can build a remarkable amount of it, and it will explain what it is doing as it goes. It has quietly lowered the barrier to creating real software more than anything I have seen in my career.
Video: a Claude Code session building a small feature
How the day actually splits
Roughly: phone while moving, chat while thinking, Claude Code while building, web when I am away from my own machines. The tool is the same intelligence throughout, so pick the door that suits the moment, and let the conversation follow you through the others.
Beyond these four, Claude also reaches into other places, an API for building it into your own products, Claude Code accessible from the mobile app for checking on long running work, and agents that operate inside Chrome, Excel, and PowerPoint. Those are for later articles. Master the four doors above first, they cover ninety five percent of daily use.